Skip to content
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

LaTeX support in tagbar vs native ctags support #837

Open
TryerGit opened this issue Oct 16, 2022 · 0 comments
Open

LaTeX support in tagbar vs native ctags support #837

TryerGit opened this issue Oct 16, 2022 · 0 comments

Comments

@TryerGit
Copy link

TryerGit commented Oct 16, 2022

Hello,

I have followed the instructions specified in tagbar.txt available at https://github.com/preservim/tagbar/blob/master/doc/tagbar.txt to set up the ~/.ctags file and made changes to the vimrc as recommended there. However, this document also states the following:

Note: As of 2012-05-05 the ctags development version contains an improved
LaTeX parser that works better than the example configuration presented here.
So if you are using a development build newer than that or a stable version
newer than 5.8 you should use the built-in support instead of this example.

Could it please be pointed out what this support is that is referred to above?

Before following the steps specified in tagbar.txt documentation, I only had the following in my vimrc (at that time I did not have a ~/.ctags file at all, nor did I have g:tagbar_type_tex set in my vimrc to what was specified in the documentation):

set tags=tags
let g:ctagscall = "ctags ".expand("%")
:autocmd BufWritePost * call system(g:ctagscall)

to automatically generate a tags file on every save operation done on the buffer. This did not produce any tags at all for the .tex file. So, to me it appears that the native pure ctags version has no support at all for .tex file.

Even though this is not a tagbar issue, I would be grateful if you could point me to where in ctags the parser is or how to enable the built-in LaTeX support in ctags as specified in the documentation above.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant