-
Notifications
You must be signed in to change notification settings - Fork 537
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
% !TEX program = latexmk -xelatex -synctex=1
doesn't work
#4347
Comments
@James-Yu I have a single tex file and a single bib file, and here is my magic: % !TEX root = myfile.tex
% !TEX program = latexmk
% !TEX options = -xelatex -synctex=1 -interaction=nonstopmode -file-line-error "%DOC%" It does work when using the aforementioned recipe. Checking the logs I see:
Any insights would be appreciated. Thanks. |
Please provide extension log. |
@James-Yu Sure thing. After closing VS code, cleaning all the auxillary files, commenting out
Then the LaTeX compiler output:
|
Will check. |
87ea37e should fix the issue. Will publish soon. |
Great that worked, thanks @James-Yu |
@James-Yu Not sure if you changed something in the past fortnight, but the issue is recurring with VS Code 1.93.0 and LaTeX Workshop 10.3.2:
|
Just double check, are you using MikTeX? Can you try out TeXLive on Windows? |
Was using MikTeX, yes. Removed that and installed TinyTeX (379MB; after installing all 44 additional packages that I use; fortunately had ~38 listed already in my README). Seems to work now without err. Both my main LaTeX and my smaller XeLaTeX document both build without issue in different [concurrently open] VS Code windows. |
Fix #4347 max-print-line should be added to string when magic tex arg is present
Pre-checks*
Environment*
The Issue*
latexmk
not executed properly with magic string, get error as if XeLaTeX:Reproduction Steps
% !TEX program = xelatex
; note that it works without error, but bibliography not added% !TEX program = latexmk -xelatex -synctex=1
and note that it doesn't workExpected Behavior
Logs
LaTeX Workshop Output*
Developer Tools Console
Anything Else?
The alternative recipe solution does work:
The text was updated successfully, but these errors were encountered: