Closed embear closed 3 years ago
Just to be sure, can you pull in and test with the latest commit c7e7d5e? The bug it was to fix is a different error but just in the off chance they are related...
I have been able to confirm this is still an issue. With the --extras=+q
option, ctags is outputing additional tags for the fully qualified tag. For cpp destructors, this now means the ~
character is no longer at the start of that particular tag entry. I have a fix ready I'll be pushing up shortly.
Example:
test test.cpp /^struct test {$/;" s line:49 file: end:52
test test.cpp /^ test() {};$/;" f line:50 struct:test file: access:public signature:() end:50
test::test test.cpp /^ test() {};$/;" f line:50 struct:test file: access:public signature:()
~test test.cpp /^ ~test() {};$/;" f line:51 struct:test file: access:public signature:() end:51
test::~test test.cpp /^ ~test() {};$/;" f line:51 struct:test file: access:public signature:()
In this case there is a tag test::~test
which is causing the substitution to fail with the ~
character.
I have the option
--extras=+q
in my global ctags configuration file~/.ctags.d/global_settings.ctags
. This option causes an error when opening the tagbar for the following simple C++ code:The tagbar window is empty and the error output is this
I'm using version 2a36ad79a7ed