From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Source Code Syntax Highlighting in Beamer slides
Date: Mon, 22 Apr 2013 08:22:14 +0200 [thread overview]
Message-ID: <20130422062214.GA15049@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <87ip3fsczj.fsf@gmail.com>
On Mon, Apr 22, 2013 at 01:03:28AM +0200, Alexander Baier wrote:
> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
> > Hello,
> >
> > Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> >
> >> Not sure why, but your -shell-escape option is being ignored. Untill
> >> you can solve this properly, maybe you can put the LaTeX calls in a
> >> shell script and set that as your org-latex-pdf-process.
> >
> > I think the problem is that the OP uses `org-latex-to-pdf-process'
> > instead of `org-latex-pdf-process'.
> >
> >
> > Regards,
>
> Hello Nicolas,
>
> You are right, using org-latex-pdf-process solves the -shell-escape
> issue and C-c C-e l P produces the PDF without compaints. Maybe the
> documentation [1] i got the code from should be updated?
Presently the manual is the most reliable source of information.
Followed by the Worg articles listed here:
<http://orgmode.org/worg/org-8.0.html>
<http://orgmode.org/worg/exporters/>
Rest of the documentation is worked on at the moment. Worg is a
community resource, so you can contribute too! There was a recent (~1
month) post by Bastien outlining a procedure to mark deprecated
documentation on Worg.
Hope this helps,
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-04-22 6:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 19:25 Source Code Syntax Highlighting in Beamer slides Alexander Baier
2013-04-21 21:08 ` Suvayu Ali
2013-04-21 22:13 ` Nicolas Goaziou
2013-04-21 23:03 ` Alexander Baier
2013-04-22 6:22 ` Suvayu Ali [this message]
2013-04-22 6:29 ` Bastien
2013-04-22 7:15 ` Suvayu Ali
2013-04-21 23:21 ` Alexander Baier
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=20130422062214.GA15049@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).