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

E40: can't open errorfile with build_dir #768

Closed
andymass opened this issue Apr 8, 2017 · 6 comments
Closed

E40: can't open errorfile with build_dir #768

andymass opened this issue Apr 8, 2017 · 6 comments

Comments

@andymass
Copy link
Contributor

andymass commented Apr 8, 2017

Explain the issue

After the switch to the new jobs backend, in non-continuous mode, the build_dir is not handled correctly when setting errorfile (cfile/cgetfile) to populate the quickfix.

Pressing \ll gives E40: can't open errorfile test.log, although the build works.
\le works correctly.

Minimal working example

\documentclass{minimal}
\begin{document}
Hello World!
\end{document}

Minimal vimrc file

set nocompatible
let &rtp  = '~/.vim/bundle/vimtex,' . &rtp
let &rtp .= ',~/.vim/bundle/vimtex/after'
filetype plugin indent on
syntax enable
let g:vimtex_compiler_latexmk = {
    \ 'continuous': 0,
    \ 'build_dir': 'build',
    \ }
@lervag
Copy link
Owner

lervag commented Apr 8, 2017

Thanks, I've reproduced this. I'll try to fix it asap.

lervag added a commit that referenced this issue Apr 8, 2017
@lervag lervag closed this as completed in adfab6e Apr 8, 2017
@lervag
Copy link
Owner

lervag commented Apr 8, 2017

I think it should be fixed now. This should also fix the same problem for the Vim jobs backend.

@andymass
Copy link
Contributor Author

andymass commented Apr 8, 2017

Works great, thanks! I'm really liking the change to the new jobs back-end so far.

@lervag
Copy link
Owner

lervag commented Apr 8, 2017

Thanks! I don't think it should have that much of an impact as long as the processes are run in the background, but perhaps it feels slightly more robust and snappy? On the code side, I think it makes things simpler and better, which is important.

@andymass
Copy link
Contributor Author

andymass commented Apr 9, 2017

If I understand correctly, prior to using job_start there was no way to receive a callback in background+non-continuous compile mode. So, for me the new way is an improvement.

@lervag
Copy link
Owner

lervag commented Apr 9, 2017

True! :)

lervag added a commit that referenced this issue Jul 7, 2021
The fix for #768 did not really work as planned, and also ruined the
exit callback without the builddir option.

refer: #768
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

2 participants