We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This bug is similar to #157.
\ll is working fine. However, I am used to type :make and usually my fingers are faster than my brain.
\ll
:make
But the makeprg is set wrong:
makeprg
:verbose set makeprg? makeprg=pdflatex -synctex=1 -interaction=nonstopmode -file-line-error-style $* Zuletzt gesetzt in ~/.vim/bundle/vim-latex/ftplugin/latex-suite/compiler.vim Zeile 37
The variable $* is not valid in vim (It is in Makefile but not in vim).
$*
Makefile
Shouldn't that set to pdflatex -synctex=1 -interaction=nonstopmode -file-line-error-style %?
pdflatex -synctex=1 -interaction=nonstopmode -file-line-error-style %
The text was updated successfully, but these errors were encountered:
Note that there are many such settings in ftplugin/latex-suite/texrc.
ftplugin/latex-suite/texrc
Sorry, something went wrong.
I never used :make myself for tex files and I also do not use vim-latex to compile my documents.
By looking at the code, it seems that the intention is to call :make filename and then, $* is replaced by filename, see, e.g., https://github.com/vim-latex/vim-latex/blob/master/ftplugin/latex-suite/compiler.vim#L146.
:make filename
filename
Hence, making :make work is not as simple as changing $* to %. Maybe the simplest workaround for you is to change your setting of makeprg.
%
No branches or pull requests
This bug is similar to #157.
\ll
is working fine. However, I am used to type:make
and usually my fingers are faster than my brain.But the
makeprg
is set wrong:The variable
$*
is not valid in vim (It is inMakefile
but not in vim).Shouldn't that set to
pdflatex -synctex=1 -interaction=nonstopmode -file-line-error-style %
?The text was updated successfully, but these errors were encountered: