From: Nick Dokos <nicholas.dokos@hp.com>
To: =?utf-8?Q?Fran=C3=A7ois?= Pinard <pinard@iro.umontreal.ca>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: About the Org documentation for minted
Date: Thu, 05 Jan 2012 02:14:43 -0500 [thread overview]
Message-ID: <14864.1325747683@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from pinard@iro.umontreal.ca (=?utf-8?Q?Fran=C3=A7ois?= Pinard) of "Wed\, 04 Jan 2012 22\:53\:06 EST." <87mxa2yfdp.fsf@iro.umontreal.ca>
François Pinard <pinard@iro.umontreal.ca> wrote:
> In org-latex.el, function org-export-as-pdf is said to "automatically
> add -shell-escape when needed", and apparently it does.
>
Well, that's what it says, but the "when needed" part is not true:
org-export-as-pdf only deals with minted, but there are other packages
that need the shell escape option to be added to the pdflatex
command. If you \usepackage{auto-pst-pdf} e.g., you'd need the shell
escape but org-export-as-pdf would not automatically add it.
> The org-export-latex-listings variable says: "In addition, it is
> necessary to install pygments (http://pygments.org), and to configure
> the variable `org-latex-to-pdf-process' so that the -shell-escape option
> is passed to pdflatex."
>
Maybe it should be fixed to say that if you use minted, then org will add
the shell escape option automatically.
> The last part of this statement is likely superfluous because of
> org-export-as-pdf, isn't it? If yes, let me suggest it is removed, so
> we are relieved from configuring the edition of org-latex-to-pdf-process
> in our ~/.emacs files.
>
> If I remove that edition and leave org-latex-to-pdf-process in ~/.emacs,
> command "C-c C-e d" still gives a fontified, colored source code in the
> genrated PDF.
>
Personally, I'd rather have it in my face that I'm doing something that
could be a security problem, than have org do it behind my back: if I
choose to override the default, it should be my decision (and the
consequences would then be my responsibility). So I'd advocate getting
rid of the automatic shell-escape and beef up the documentation
instead. But I'm probably in a tiny minority here.
Nick
PS. The relevant commit is 3ed5915f01ac5647db5f2204dc695519653b1190
and there is probably discussion on the ML about it, but I haven't gone
back to review it.
prev parent reply other threads:[~2012-01-05 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 3:53 About the Org documentation for minted François Pinard
2012-01-05 4:33 ` François Pinard
2012-01-05 7:14 ` Nick Dokos [this message]
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=14864.1325747683@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=pinard@iro.umontreal.ca \
/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).