-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Add an option for -shell-escape #969
Comments
+1 .... |
👍 |
👍 Really need this (might also be of use to add a generic option for extra LaTeX flags). |
We now have |
I get an empty space instead of highlighted LaTeX code with the following code. I have added the minted package in a template. To get the right output, I have to compile the generated TeX file with -shell-escape option before the file name. I was wondering if someone has an example of using -shell-escape that works. title: "Code Chunk with Highlight" fonttheme: structureboldBasic - Interfaces {.fragile}
\begin{minted}{latex} |
I don't know what version of pandoc you're using, but +++ Behzad Samadi [Nov 05 15 08:11 ]:
|
I was using 1.15.0.6. and then I updated to 1.15.1.1. The issue was the same. |
I assume you're running pandoc via some kind of wrapper +++ Behzad Samadi [Nov 05 15 11:54 ]:
|
Yes. I am using RStudio. When I use: |
@bsamadi I'm confused about what problem you're encountering, if any. |
John, I am able to generate the PDF with no error but instead of the highlighted code, I get an empty space. If I compile the generated tex file, I then get the right output. Does the pandoc job finishes with generating the tex file? If that is the case, then the problem is with RStudio and the way it calls pdflatex. |
I have the exact same issue as @bsamadi: There is only empty space. I am running pandoc % --output=file.pdf --latex-engine=pdflatex --latex-engine-opt="-shell-escape" No RStudio, just editing the file in vim. |
@Lesik I'm not sure, but this is a closed issue. |
We can't always tell if it's LaTeX, ConTeXt, or plain TeX. Better just to use "tex" always. Also changed: ConTeXt writer: now outputs raw "tex" blocks as well as "context". (Closes #969). RST writer: uses ".. raw:: latex" for "tex" content. (RST doesn't support raw context anyway.) Note that if "context" or "latex" specifically is desired, you can still force that in a markdown document by using the raw attribute (see MANUAL.txt): ```{=latex} \foo ``` Note that this change may affect some filters, if they assume that raw tex parsed by the Markdown reader will be RawBlock (Format "latex"). In most cases it should be trivial to modify the filters to accept "tex" as well.
Hi,
Would it be difficult to add an option to call LaTeX with the
-shell-escape
flag when compiling to PDF? My use-case is custom minted blocks that I'm adding directly, and this package requires latex to be called with the flag. Granted, I could generate .tex and then compile it myself, but it would definitely be more convenient to have pandoc add the right flag :).Thanks,
jonathan
The text was updated successfully, but these errors were encountered: