From: Daniel Fleischer <danflscr@gmail.com>
To: Younes Ben El <younes.brovi@gmail.com>
Cc: 50555@debbugs.gnu.org
Subject: bug#50555: [BUG] Org Latex export doesn't handle src blocks correctly
Date: Sat, 18 Sep 2021 22:45:44 +0300 [thread overview]
Message-ID: <m2ee9lis5z.fsf@gmail.com> (raw)
In-Reply-To: <87y27uueuo.fsf@gmail.com> (Younes Ben El's message of "Sat, 18 Sep 2021 15:38:13 +0100")
I verified again, this time with emacs -Q; the empty argument list []
does NOT stop you from compiling org into PDF.
> (with-eval-after-load 'ox-latex
> (add-to-list 'org-latex-packages-alist '("" "minted"))
> (setq org-latex-listings 'minted)
> (setq org-latex-pdf-process
> '("pdflatex -shell-escape -interaction nonstopmode -output-directory %o %f"
> "pdflatex -shell-escape -interaction nonstopmode -output-directory %o %f"
> "pdflatex -shell-escape -interaction nonstopmode -output-directory %o %f")))
>
Here is the hint: since "minted" is using a python package (pygments) for
the highlighting, one need to add the "-shell-escape" to the call. Other
than that, everything works as planned. Since it's a specific
configuration for using "minted", I'll add a comment in the manual.
If you feel that there is still an issue with the [], please provide an
emacs -Q recipe that shows it, after adding the "-shell-escape" flag.
--
Daniel Fleischer
next prev parent reply other threads:[~2021-09-18 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAM66s7Ej_i8tep4vaOyb8Uv-zNpeA-N7E2d+C1yctSCuwkrMA@mail.gmail.com>
2021-09-18 10:57 ` bug#50555: [BUG] Org Latex export doesn't handle src blocks correctly Daniel Fleischer
2021-09-18 14:38 ` Younes Ben El
2021-09-18 19:45 ` Daniel Fleischer [this message]
2021-09-18 19:53 ` Younes Ben El
2021-09-18 20:04 ` bug#50555: [PATCH] " Daniel Fleischer
2021-09-27 8:29 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2ee9lis5z.fsf@gmail.com \
--to=danflscr@gmail.com \
--cc=50555@debbugs.gnu.org \
--cc=younes.brovi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).