Closed TheOfficialDarthVader closed 3 years ago
As a quick sanity check, try setting your toolchain to just latexmk --version
to ensure it's not something with your PDF?
That command fails to run
You seem to have some other issues here, I would create a debugging .bat
or .cmd
file to print out paths (where latexmk
) and env variables among other things to confirm everything is correct.
If Perl is not found, normally you get something along the lines of latexmk.exe: The script engine could not be found.
IIRC...
Unfortunately, this is not really something the package can solve.
Rather frustratingly a restart seems to have fixed the problem. I find this a bit unusual as changes to environment variables are applied immediately. And restarting any program looking for said variable in theory should fix the problem. Guess this comes down to an idiosyncrasy in windows somewhere...
What I've done:
atom-latex
latexmk
using the MikTex ConsoleC:\Perl64\bin
C:\Program Files\MiKTeX 2.9\miktex\bin
andC:\Program Files\MiKTeX 2.9\miktex\bin\x64\
I can confirm that Perl works as I am able to run both it and the
latexmk
script from Command Prompt. I can also uselatexmk
from TexStudio, but this required settingCommands ($PATH)
toC:\Perl64\bin
. I can runpdflatex
as the build engine inatom-latex
. It is justlatexmk
that is not working.Given what I had to do to get Perl scripts to work with TexStudio this would seem to suggest the Environment Variables being passed are in some way incorrect.
The build log is just a single line:
> latexmk -synctex=1 -interaction=nonstopmode -file-line-error -pdf "Cover Letter"
So I'm not sure where it is getting hung up, I assume it is an issue with not finding Perl.