-
Notifications
You must be signed in to change notification settings - Fork 391
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
"Something went wrong when parsing log files!" during quickly repeated single shot compilations #2225
Comments
Strange. This is obviously not a "pure" VimTeX issue, but it may be possible to resolve it within VimTeX. It seems the problem may be caused by the timing of the callback. I.e., it seems that, in some cases, the callback is issued when the airline code is executing, and that this involves a context where I would prefer to better understand the issue and possibly be able to reproduce it. Still, I can understand that it can be more or less impossible in such cases, so I'll go for the quickfix. Let me know if my recent push solves the issue for you. |
You may have pushed to the wrong branch however. @lervag |
Oops! I'll fix that; sorry! |
Fixed! |
It seems to work (or at least makes it even less reproducible :). Thanks a lot. |
Great, glad to hear it; feel free to reopen or open a new issue if you should continue to experience this. |
Description
I have a relatively long LaTeX document which needs ~4s for a single compilation, more when more passes are required. I have a key mapped to VimtexCompileSS and it happens that I start a new compilation while an old one is still running. Then, occasionally, the following error message appears:
I do not know if it is vim-airline or vimtex problem, I ask here first, since the
cclose
command is invimtex/qf.vim
.I am ready to do some testing/small coding, but a hint where to start would be welcomed.
Steps to reproduce
It is not completely easy to reproduce, it seems to happen by long Latex files only.
Expected behavior
No response
Actual behavior
No response
Do you use a latexmkrc file?
It is not latexmk specific. Infact it happens with latexrun and latexmk.
VimtexInfo
The text was updated successfully, but these errors were encountered: