-
Notifications
You must be signed in to change notification settings - Fork 390
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
latexmain specifier does not work unless the mainfile includes the current file? #2831
Comments
If the file is not included, then how can we claim that the specified mainfile is really a main file? I find the current behaviour to make a lot of sense, so if anything, I would prefer to update the docs. |
Also fine by me. (it may also be preferable to send a warning message inform the user that latexmain configuration is ignored.) |
I believe I answered hastily. The touch test.tex
touch main.tex
touch main.tex.latexmain
nvim test.tex Doing the above, then
Notice that it finds |
Yes, but if there are two candidate main files (Actual use case: the Napkin compiles really slowly, so I use a trick to copy the generated PDF file to a backup after each compilation pass, but I also want the forward/reverse search in vimtex to work and use the "Napkin-backup.pdf" file.) |
Hmm, ok. Perhaps I'll add a warning in this case, then. I agree it can be considered confusing, although I still think the current actual behaviour is correct. |
Description
When I try to use .latexmain file as mentioned in "File .latexmain specifier" section of the documentation,
This is according to the behavior in the source code:
vimtex/autoload/vimtex/state.vim
Line 359 in a630f0f
The corresponding documentation:
vimtex/doc/vimtex.txt
Line 431 in a630f0f
I think this is mostly a documentation bug (nevertheless, would it be preferable to edit the source code instead to use that file as main regardless?)
The text was updated successfully, but these errors were encountered: