-
Notifications
You must be signed in to change notification settings - Fork 624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't pre-process the macro but it works with Exuberant Ctags 5.8 #2356
Comments
C parser is completely rewritten in u-ctags. Please, use -D option as shown below.
|
Thanks for the quick response. will you deliver an enhancement? |
Yes, but I will take more than 1 year to implement it. ctags itself knows the definitions of macro.
So ctags can prepare the arugments for -D option by itself. I had a prototype and it worked. However, what I have to do is written in #1038 . |
Look forward to that release. BTY, this is really a great tool. |
We added so many features, so I cannot remember them timely. If it is acceptable to run ctags twice, you don't have to specify -D option manually.
@pragmaware, you may be interested in this output. |
runs old C parser inherited from Exuberant Ctags. (But we will not fix the bug for it even if we got a bug report.) |
See #2427. |
- new sections: - Does Universal Ctags support Unicode file names? - Why does zsh cause "zsh: no matches found" error? - add TODO comment for universal-ctags#1421, universal-ctags#2356, and universal-ctags#2540
- new sections: - Does Universal Ctags support Unicode file names? - Why does zsh cause "zsh: no matches found" error? - add TODO comment for universal-ctags#1421, universal-ctags#2356, and universal-ctags#2540
(
Thank you for contacting us.
If you are reporting an issue with the parsing output, please fill
the following template. As your custom CTags configuration can
affect results, please always use
--options=NONE
as the firstoption when running
ctags
.Otherwise, delete the template and write your issue from scratch.
Examples may help developers understanding your issue better.
Use GitHub web interface and markdown notation.
Using mail results broken text rendering that makes
the developers go crazy.
)
The name of the parser:
c/c++
The command line you used to run ctags:
The content of input file:
FTNC /u/yanchen/.FAST_9995.src.c 6562;" kind:f line:6562 language:C typeref:typename:void signature:(etmif_set_argv) end:6666
The tags output you expect:
The version of ctags:
The text was updated successfully, but these errors were encountered: