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

"Something went wrong when parsing log files!" during quickly repeated single shot compilations #2225

Closed
ji-cerny opened this issue Oct 29, 2021 · 6 comments
Labels

Comments

@ji-cerny
Copy link

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:

VimTeX: Something went wrong when parsing log files!
Error detected while processing function airline#extensions#vimtex#get_scope[20]..311[1]..<SNR>97_callback[1]..vim
tex#compiler#callback[54]..vimtex#qf#open[19]..function airline#extensions#vimtex#get_scope[20]..311[1]..<SNR>97_c
allback[1]..vimtex#compiler#callback[54]..vimtex#qf#open:
line   16:
E565: Not allowed to change text or change window:       cclose
Press ENTER or type command to continue

I do not know if it is vim-airline or vimtex problem, I ask here first, since the cclose command is in vimtex/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

System info
  OS: Fedora release 35 (Thirty Five)
  Vim version: VIM 8.2 (1-3404)
  Has clientserver: true
  Servername: VIM

VimTeX project: foo
  base: foo.tex
  root: /home/cerny/foo/
  tex: /home/cerny/foo/foo.tex
  main parser: current file verified
  document class: scrbook
  packages: alltt amsbsy amsfonts amsgen amsmath amsopn amssymb amstext amsthm array atbegshi atbegshi-ltx atverye
  compiler: latexmk
    engine: -pdf
    options:
      -verbose
      -file-line-error
      -synctex=1
      -interaction=nonstopmode
    callback: 1
    continuous: 1
    executable: latexmk
    job: 
      jobid: process 910791 dead
      output: /tmp/vvk9LKb/0
      cmd: max_print_line=2000 latexmk -verbose -file-line-error -synctex=1 -interaction=nonstopmode -pdf 'EiS.tex
      pid: 910791
  viewer: General
  qf method: LaTeX logfile
@ji-cerny ji-cerny added the bug label Oct 29, 2021
@lervag
Copy link
Owner

lervag commented Oct 29, 2021

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: ...

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 cclose is not allowed.

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.

@lervag lervag closed this as completed Oct 29, 2021
@user202729
Copy link

You may have pushed to the wrong branch however. @lervag

@lervag
Copy link
Owner

lervag commented Oct 29, 2021

Oops! I'll fix that; sorry!

lervag added a commit that referenced this issue Oct 29, 2021
@lervag
Copy link
Owner

lervag commented Oct 29, 2021

Fixed!

@ji-cerny
Copy link
Author

It seems to work (or at least makes it even less reproducible :). Thanks a lot.

@lervag
Copy link
Owner

lervag commented Oct 29, 2021

Great, glad to hear it; feel free to reopen or open a new issue if you should continue to experience this.

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

No branches or pull requests

3 participants