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

doc: Note on lazy loading and inverse search #2560

Merged
merged 1 commit into from
Nov 6, 2022

Conversation

shuber2
Copy link
Contributor

@shuber2 shuber2 commented Nov 5, 2022

The provided command lines for inverse search do not work when VimTeX is loaded lazily only for tex files, as provided by various plugin managers. Add a note on how to cope with that.

@lervag
Copy link
Owner

lervag commented Nov 6, 2022

I don't agree with this, because there is simply no reason to lazily load VimTeX. It is already lazily loaded by virtue of being a filetype plugin. People should not cope with it as you suggest, they should just not lazily load VimTeX.

However, it may be worth mentioning this somewhere, because this particular issue does show up once in a while. Perhaps we should add a note in the README?

Using lazy loading of certain plugin managers with VimTeX is
discouraged. Add a note on this in installation notes in the README. One
particular reason is a complication for inverse search. Add a
corresponding note in the documentation.
@shuber2
Copy link
Contributor Author

shuber2 commented Nov 6, 2022

That is a good and valid point. Thank you for pointing it out. I changed the proposed pull request to adding notes on discouragement of lazy loading VimTeX.

lervag added a commit that referenced this pull request Nov 6, 2022
@lervag lervag merged commit 5e8a8d9 into lervag:master Nov 6, 2022
@lervag
Copy link
Owner

lervag commented Nov 6, 2022

Thanks! I took the liberty of rephrasing it while merging.

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

Successfully merging this pull request may close these issues.

2 participants