gpt4 book ai didi

linux - 为什么 ctags -R 。不为子目录中的源代码生成索引?

转载 作者:塔克拉玛干 更新时间:2023-11-02 23:30:23 27 4
gpt4 key购买 nike

当前目录:

[mirror@home libevent]$ ls
arc4random.c bufferevent_sock.c epoll.c event_tagging.c evutil.c l Makefile.am strlcpy-internal.h
autogen.sh buffer_iocp.c epoll_sub.c evmap.c evutil_rand.c libevent_openssl.pc.in Makefile.nmake test
b changelist-internal.h evbuffer-internal.h evmap-internal.h evutil_time.c libevent.pc.in minheap-internal.h time-internal.h
buffer.c ChangeLog evconfig-private.h.in evport.c ht-internal.h libevent_pthreads.pc.in mm-internal.h util-internal.h
bufferevent_async.c ChangeLog-1.4 evdns.3 evrpc.c http.c LICENSE poll.c whatsnew-2.0.txt
bufferevent.c ChangeLog-2.0 evdns.c evrpc-internal.h http-internal.h listener.c ratelim-internal.h whatsnew-2.1.txt
bufferevent_filter.c compat event.3 evsignal-internal.h include log.c README WIN32-Code
bufferevent-internal.h configure.in event.c evthread.c iocp-internal.h log-internal.h sample win32select.c
bufferevent_openssl.c defer-internal.h event-internal.h evthread-internal.h ipv6-internal.h m4 select.c
bufferevent_pair.c devpoll.c event_iocp.c evthread_pthread.c kqueue.c make_epoll_table.py signal.c
bufferevent_ratelim.c Doxyfile event_rpcgen.py evthread_win32.c kqueue-internal.h make-event-config.sed strlcpy.c

测试目录下有一些文件:

[mirror@home libevent]$ ls test/
bench.c Makefile.am regress_dns.c regress_listener.c regress_ssl.c regress_zlib.c test-fdleak.c test-time.c tinytest_local.h
bench_cascade.c Makefile.nmake regress_et.c regress_main.c regress_testutils.c rpcgen_wrapper.sh test-init.c test-weof.c tinytest_macros.h
bench_http.c regress_buffer.c regress.h regress_minheap.c regress_testutils.h test-changelist.c test-ratelim.c tinytest.c
bench_httpclient.c regress_bufferevent.c regress_http.c regress.rpc regress_thread.c test-dumpevents.c test-ratelim.sh tinytest_demo.c
check-dumpevents.py regress.c regress_iocp.c regress_rpc.c regress_util.c test-eof.c test.sh

test目录下有很多文件有main()函数:

[mirror@home libevent]$ find test/ -regex .*.c -exec grep main {} +
test/regress.c:struct testcase_t main_testcases[] = {
test/test-weof.c:main(int argc, char **argv)
test/regress_dns.c:/* FIXME: We should move this to regress_main.c if anything else needs it.*/
test/regress_buffer.c: size_t remaining;
test/regress_buffer.c: remaining = v[0].iov_len - 512;
test/regress_buffer.c: tt_int_op(remaining, ==, v[0].iov_len);
test/regress_buffer.c: remaining -= 8;
test/regress_buffer.c: n = evbuffer_reserve_space(buf, remaining+64, v, 2);
test/regress_buffer.c: tt_int_op(remaining, ==, v[0].iov_len);
test/regress_buffer.c: remaining -= 1;
test/regress_buffer.c: n = evbuffer_reserve_space(buf, remaining+64, v, 2);
test/regress_buffer.c: tt_int_op(remaining, ==, v[0].iov_len);
test/regress_buffer.c: /* Drain some of the remaining chunk, then add it to another buffer */
test/regress_main.c: { "main/", main_testcases },
test/regress_main.c:main(int argc, const char **argv)
test/regress_main.c: if (tinytest_main(argc,argv,testgroups))
test/tinytest.c:static int in_tinytest_main = 0; /**< true if we're in tinytest_main().*/
test/tinytest.c: if (!in_tinytest_main) {
test/tinytest.c: " called from within tinytest_main.\n");
test/tinytest.c:tinytest_main(int c, const char **v, struct testgroup_t *groups)
test/tinytest.c: ++in_tinytest_main;
test/tinytest.c: --in_tinytest_main;
test/test-eof.c:main(int argc, char **argv)
test/test-ratelim.c:main(int argc, char **argv)
test/tinytest_demo.c:main(int c, const char **v)
test/tinytest_demo.c: /* Finally, just call tinytest_main(). It lets you specify verbose
test/tinytest_demo.c: return tinytest_main(c, v, groups);
test/test-time.c:main(int argc, char **argv)
test/bench_cascade.c:main(int argc, char **argv)
test/test-dumpevents.c: remain in the future.
test/test-dumpevents.c:main(int argc, char **argv)
test/test-changelist.c:main(int argc, char **argv)
test/test-init.c:main(int argc, char **argv)
test/test-fdleak.c:main(int argc, char **argv)
test/bench_http.c:main(int argc, char **argv)
test/bench.c:main(int argc, char **argv)
test/bench_httpclient.c:main(int argc, char **argv)

但在我使用之后:

ctags -R .

打开vim,然后

:tag main
:g ]

状态栏只显示:

E433: No tags file
E426: tag not found: main

怎么了? 标签文件已经加载,为什么没有标签文件?令人困惑...

似乎由 ctags 生成的索引包含这些文件,其中包含主要功能:

3643 main    sample/dns-example.c    /^main(int c, char **v) {$/;"   f
3644 main sample/event-read-fifo.c /^main(int argc, char **argv)$/;" f
3645 main sample/hello-world.c /^main(int argc, char **argv)$/;" f
3646 main sample/http-server.c /^main(int argc, char **argv)$/;" f
3647 main sample/le-proxy.c /^main(int argc, char **argv)$/;" f
3648 main sample/signal-test.c /^main(int argc, char **argv)$/;" f
3649 main sample/time-test.c /^main(int argc, char **argv)$/;" f
3650 main test/bench.c /^main(int argc, char **argv)$/;" f
3651 main test/bench_cascade.c /^main(int argc, char **argv)$/;" f
3652 main test/bench_http.c /^main(int argc, char **argv)$/;" f
3653 main test/bench_httpclient.c /^main(int argc, char **argv)$/;" f
3654 main test/regress_main.c /^main(int argc, const char **argv)$/;" f
3655 main test/test-changelist.c /^main(int argc, char **argv)$/;" f
3656 main test/test-dumpevents.c /^main(int argc, char **argv)$/;" f
3657 main test/test-eof.c /^main(int argc, char **argv)$/;" f
3658 main test/test-fdleak.c /^main(int argc, char **argv)$/;" f
3659 main test/test-init.c /^main(int argc, char **argv)$/;" f
3660 main test/test-ratelim.c /^main(int argc, char **argv)$/;" f
3661 main test/test-time.c /^main(int argc, char **argv)$/;" f
3662 main test/test-weof.c /^main(int argc, char **argv)$/;" f
3663 main test/tinytest_demo.c /^main(int c, const char **v)$/;" f
3664 main_callback sample/dns-example.c /^main_callback(int result, char type, int count, int ttl,$/;" f file:
3665 main_testcases test/regress.c /^struct testcase_t main_testcases[] = {$/;" v typeref:struct:testcase_t

但是为什么tag main,g]找不到包含main函数的文件列表呢?

即使启用了 autochdir,romainl 的解决方案也适用于 :tag name

我已经运行了 :set tags=./tags,tags,因为启用了 autochdir,即使当前目录更改为其他目录,它也能正常工作,但 g ] 有时可能无法工作,为什么?

但 g ] 有时不起作用:

错误信息是E257: cstag: tag not found

编辑 2:.vimrc 的内容

cat ~/.vimrc
set autoindent
colorscheme desert
set number

最佳答案

E433 错误意味着 Vim 没有找到您的 tags 文件,所以,不,tags 文件还没有加载。

键入 :set tags 应该输出如下内容:

./tags,tags

这是默认值,意思是“在当前目录中然后查找位于当前文件目录中的tags文件”。

因为您有set autochdir,所以您最终可能会进入一个没有tags 文件的目录。例如,在 test 中。

要确保 Vim 找到你的 tags 文件,你应该使用像这样的东西:

set tags=./tags,tags;$HOME

意思是“在当前目录then中的任何父目录中查找位于当前文件then目录下的tags文件直到 $HOME”。

编辑

好吧,上面的设置对我来说已经按预期工作了很长时间。但这是我刚刚做的小实验(当然是使用 set autochdir):

  1. 我在 ~/workspace/accordion/ 中,其中仅包含一个文件 accordion.js

  2. 我执行 $ ctags -R .:~/workspace/accordion/tags 已创建。

  3. 我做 $ mkdir -p aa/bb/cc/dd/ee/ff

  4. 我做 $ vim aa/bb/cc/dd/ee/ff/test.js

  5. 在 Vim 中,我执行 :tag *mini 跳转到 mini() 方法的声明,Accordion() 的成员 构造函数位于 ~/workspace/accordion/accordion.js 中,符合预期

因为我的 ~/.vimrc 中有 set tags=./tags,tags;$HOME Vim 正确地从一个目录爬到另一个目录,直到它到达 ~/worspace/accordion/tags。即使我深陷在一个不切实际的深文件树中。

Is there an accordion/aa/bb/cc/dd/ee/ff/tags ? no, let's go up…
Is there an accordion/aa/bb/cc/dd/ee/tags ? no, let's go up…
Is there an accordion/aa/bb/cc/dd/tags ? no, let's go up…
Is there an accordion/aa/bb/cc/tags ? no, let's go up…
Is there an accordion/aa/bb/tags ? no, let's go up…
Is there an accordion/aa/tags ? no, let's go up…
Is there an accordion/tags ? yes! let's scan it!

正如另一位评论者反复问你但没有成功,当你在子目录中时 :pwd 的输出是什么?这是另一个请求::call tagfiles() 的输出是什么?

关于linux - 为什么 ctags -R 。不为子目录中的源代码生成索引?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/12541403/

27 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com