You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I'm having some trouble to run minted with my miktex. I've read #419, which seems related, but doesn't help as the cases mentioned there doesn't really match my case.
The error is the same though:
Package minted Error: minted v3+ executable is not installed, is not added to
PATH, or is not permitted with restricted shell escape; or MiKTeX is being use
d with -aux-directory or -output-directory without setting a TEXMF_OUTPUT_DIREC
TORY environment variable.
And here are some information that may be helpful:
$ miktex --version
One MiKTeX Utility 1.9 (MiKTeX 24.1)
This should rule out the possibility of minted not installed / added to PATH:
$ latexminted --version
latexminted 0.3.2
Python executable for the LaTeX minted package
Libraries: latex2pydata 0.4.1, latexrestricted 0.6.2, pygments 2.18.0
This should rule out the necessity for shell escape:
You could compile a simple document with just a single minted command or environment, and post the document plus complete log here.
If you're using an editor to compile, you might try using the command line instead, since sometimes editors modify PATH.
You could try something like \input{|"where latexminted"} (needs MiKTeX --enable-pipes) to see whether the document can correctly find latexminted, but then latexminted or minted is failing in some way.
Hi! I'm having some trouble to run minted with my miktex. I've read #419, which seems related, but doesn't help as the cases mentioned there doesn't really match my case.
The error is the same though:
And here are some information that may be helpful:
This should rule out the possibility of minted not installed / added to PATH:
This should rule out the necessity for shell escape:
And I'm running with
$ pdflatex .\nt.tex
, which make TEXMF_OUTPUT_DIRECTORY irrelevantTORY environment variable.
I wonder what the problem could be. Or are there any more logs that could be helpful for tracking down the problem?
Thank you so much!
The text was updated successfully, but these errors were encountered: