Skip to content
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

-shell-escape is not properly passed #166

Open
bazzilic opened this issue Aug 10, 2017 · 5 comments
Open

-shell-escape is not properly passed #166

bazzilic opened this issue Aug 10, 2017 · 5 comments
Labels

Comments

@bazzilic
Copy link

I am trying to use minted on Windows (Atom, MiKTeX, Python 2, pygments—all properly installed and updated to latest versions), which requires -shell-escape. The .tex document has % !TEX option = -shell-escape in the first line, and when I look in the LaTeXTools Console output I can see that it is passed to texify:

Platform: win32; texpath:
Processing file Assignment.tex (Assignment) in directory C:\Users\bazzilic\Dropbox\My Projects\TestAssignment\AssignmentDocument
texify builder
texify -p --tex-option="-interaction=nonstopmode" --engine=pdftex --tex-option="--synctex=1 -shell-escape" "Assignment.tex"

However, right after that the log says:

Parsing C:\Users\bazzilic\Dropbox\My Projects\TestAssignment\AssignmentDocument\Assignment.log
ERRORS:
C:/Users/bazzilic/Dropbox/My Projects/TestAssignment/AssignmentDocument/Assignment.tex:11: Package minted Error: You must invoke LaTeX with the -shell-escape flag. [\usepackage]

Am I doing something wrong? Is this a bug? This same document used to compile fine about half a year ago btw.

@r-stein
Copy link

r-stein commented Aug 10, 2017

You may try % !TEX option = --shell-escape

@bazzilic
Copy link
Author

I tried --shell-escape, I tried options (plural), I tried %! instead of % !. No effect.

@ig0774 ig0774 added the bug label Aug 10, 2017
@ig0774
Copy link
Collaborator

ig0774 commented Aug 10, 2017

I think this is a straightforward error in how we are passing options to texify.

@bazzilic
Copy link
Author

I see that latest commit to the repo is in 2016. Is this project still active?

@bazzilic
Copy link
Author

bazzilic commented Dec 7, 2017

I assume, this will not be fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants