Replies: 1 comment 1 reply
-
Actually this issue should not have been closed yet again. Not sure why it was (doesn't make me - as someone who has a great deal of respect for this extension - feel very good) It is clearly a bug and can easily be resolved by adding the
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Disable all the other extensions except for LaTeX Workshop, restart VS Code, and check that you still see this issue. [Required]
You still see this issue?: Yes
Make sure to visit the wiki FAQ before filling an issue.
You visited the wiki?: Yes
Describe the bug [Required]
This has to do with #2910 which has been locked but which should be potentially fixable. In that previous issue the "bug" - in other words the failure of Windows files to compile with Luatex when there was a space in the filename or path was attributed to "We can do nothing on our side. This is related to latexmk and lualatex."
I was surprised to see this - because the Latex extension in Atom (which I have abandoned in favour of this great extension) copes with LuaTex files with spaces on Windows perfectly well.
as it happens the error can be corrected quite easily on a one-off basis by including a .latexmkrc file with the line
$MSWin_back_slash = 0; in the folder of the source tex file.
I'm not sure how Latex on Atom gets around this problem, but clearly it is possible without having to resort to individual local latexmkrc files.
To Reproduce
As #2910
then add the correcting file
Expected behavior
Since Atom Latex managed to resolve this problem, it seems likely that Latex-Workshop can achieve this as well, which would be good. It is not a fixed issue on the latexmk side.
Desktop [Required]
Beta Was this translation helpful? Give feedback.
All reactions