raven42
commented
3 years ago So there are three questions here. First is an easier one to handle the C++ output, next we need ctags to output the correct output for the markdown language, and third more to your specific question is the way the tags are displayed. I'll do my best to answer each as best I can.
C++ tag output
For the cpp file, the ctags command you are referencing is a little different than what tagbar executes. The command as tagbar executes it is as follows, and results in the following output of the test.cpp file you provided:
ctags --extras=+F -f - --format=2 --excmd=pattern --fields=nksSafet --sort=no --append=no -V --language-force=c++ --c++-kinds=hdpgetncsufmv test.cpp Option: --language-force=c++
Option: --c++-kinds=hdpgetncsufmv
Initialize parser: C++
Initialize parser: QtMoc
Reading command line arguments
OPENING test2.cpp as C++ language file [new]
Initialize parser: CPreProcessor
Foo test2.cpp /^class Foo$/;" c line:1 file: end:5
foo_method test2.cpp /^ void foo_method();$/;" p line:4 class:Foo typeref:typename:void file: access:public signature:() end:4
Bar test2.cpp /^class Bar$/;" c line:7 file: end:11
bar_method test2.cpp /^ void bar_method();$/;" p line:10 class:Bar typeref:typename:void file: access:public signature:() end:10Specifically missing is the --extras=+F flag to include file scope for tags, and the --c++-kinds definition telling it what all to find.
Tagbar version
But it looks like in your case, we have two problems. Not only is the tagbar definition for markdown inaccurate (discussed below), but it also looks like your version of universal ctags is a little older (compiled 2 years ago). I'm not an expert on universal ctags, but I'm taking a guess that the markdown language has added additional support since then. As such, the scope information is not visible in your output, where in my test it was visible using the same file and command.
ctags --extras=+F -f - --format=2 --excmd=pattern --fields=nksSafet --sort=no --append=no -V test.md
Reading command line arguments
Get file language for test.md
pattern: test.md
#candidates: 1
0: Markdown (extension: "md")
#candidates after sorting and filtering: 1
0: Markdown (extension: "md")
OPENING test.md as Markdown language file [new]
Initialize parser: Markdown
... // output truncated
My chapter test.md /^# My chapter$/;" c line:1 end:7
My section test.md /^## My section$/;" s line:2 chapter:My chapter end:7
My sub section test.md /^### My sub section$/;" S line:3 section:My chapter""My section end:7
The last chapter test.md /^# The last chapter$/;" c line:7 end:9
The last section test.md /^## The last section$/;" s line:8 chapter:The last chapter end:9
The last sub section test.md /^### The last sub section$/;" S line:9 section:The last chapter""The last section end:9If you notice in the output after the line numbers, there is additional information regarding the scope of the tag and it's corresponding parent sections. So compiling a new version of universal ctags might get this part fixed for you.
Markdown language support for tagbar
Now as for your more pertinent question about the markdown, I believe this is due to a lack of a correct markdown definition in tagbar for the different tag kinds and scope information. By default tagbar is always going to group similar tag kinds together, so in the case of markdown, all chapters will be grouped together, all sections will be grouped together, and so on. However the definition for tagbar's markdown language support simply calls each section h1, h2, and so forth for the different heading levels. Also there is an option where tagbar can provide scope information though as well to ensure that tag kinds that are scoped can show the proper hierarchy, but for the markdown language, that is currently not implemented in tagbar.
To fix this, there are two ways we can do it. First option is a local definition in your .vimrc to override the default markdown language definition for tagbar. That can be done by adding the following in your .vimrc. This will rename the tag kinds to be more accurate for what ctags outputs, and also provide the scope2kind and kind2scope definitions needed to get the proper scope hierarchy.
let g:tagbar_type_markdown = {
\ 'ctagstype' : 'markdown',
\ 'kinds' : [
\ 'c:chapter:0:1',
\ 's:section:0:1',
\ 'S:subsection:0:1',
\ 't:subsubsection:0:1',
\ 'T:l4subsection:0:1',
\ 'u:l5subsection:0:1',
\ ],
\ 'sro' : '""',
\ 'kind2scope' : {
\ 'c' : 'chapter',
\ 's' : 'section',
\ 'S' : 'subsection',
\ 't' : 'subsubsection',
\ 'T' : 'l4subsection',
\ },
\ 'scope2kind' : {
\ 'chapter' : 'c',
\ 'section' : 's',
\ 'subsection' : 'S',
\ 'subsubsection' : 't',
\ 'l4subsection' : 'T',
\ },
\ }
The second option would be to provide a fix for this for all users in the uctags.vim file in tagbar. This could be derived from the above output to correct the tagbar definition for the markdown language. I will defer to someone who works with markdown more specifically to implement this as I do not write anything in markdown and so I'm not in the best position to test or validate.
With either of the solutions, you should see output like this:
" Press <F1>, ? for help
▼ My chapter : #
▼ My section : ##
My sub section : ###
▼ The last chapter : #
▼ The last section : ##
The last sub section : ###Hope this helps.
hholst80
alerque
How can I disable the group-by operation applied by Tagbar?
Input document:
Test.md
Config:
The expected result should be something similar to what ctags emit (explicitly unsorted)
I leave it open that my ctags version is completely incompatible with Tagbar because the following C++ file is interpreted correctly by Tagbar but the suggested ctags command emits nothing.