emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: LaTeX minted --shell-escape error after updating to 8.0.3
Date: Mon, 27 May 2013 18:16:39 -0400	[thread overview]
Message-ID: <87d2scm5ko.fsf@pierrot.dokosmarshall.org> (raw)
In-Reply-To: CAG+C5iu2VMLaheyYKUb9WFKMffY_vmazb4jQwA9V2XRc_cazmQ@mail.gmail.com

Senthil Kumar M <senthil.debian@gmail.com> writes:

>>> Is there any variable that had changed and need to be set for the
>>> syntax highlighting to work properly?
>>>
>>
>> I don't think so. My guess is that your minted/pygments installation is
>> broken, i.e. nothing to do with org. What happens if you leave org out
>> of the equation altogether? I.e. take a simple tex file using minted and
>> pass it through ``pdflatex --shell-escap''?
>>
>
> If I run "pdflatex --shell-escape foo.tex" on the terminal, it gives
> the same result (i.e. no colour highlighting).
>

[Given Suvayu's answer, the following is irrelevant to this
 case. Nevertheless, these are basic things that one should do when
 something goes wrong, which is why I'm following up.]]

Was foo.tex what org produced or did you create it by hand? If the
former, did you look at foo.tex? Did it contain a minted environment?

> While writing this reply, I saw the email from Suvayu Ali, about
> changing org-export-latex-listings to org-latex-listings. That solved
> this issue!
>

Yup, I saw it too and kicked myself!

-- 
Nick

      reply	other threads:[~2013-05-27 22:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-26  1:53 LaTeX minted --shell-escape error after updating to 8.0.3 Senthil Kumar M
2013-05-26  6:44 ` Nick Dokos
2013-05-27 19:31   ` Senthil Kumar M
2013-05-27 20:17     ` Nick Dokos
2013-05-27 20:40       ` Suvayu Ali
2013-05-27 20:46       ` Senthil Kumar M
2013-05-27 22:16         ` 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=87d2scm5ko.fsf@pierrot.dokosmarshall.org \
    --to=ndokos@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).