From: Richard Lawrence <firstname.lastname@example.org>
Cc: Ken Mankoff <email@example.com>
Subject: Re: minted in Org 8.6
Date: Tue, 29 Apr 2014 08:43:25 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Ken Mankoff <email@example.com> writes:
> #+begin_src emacs-lisp
> ;; minted latex export
> (setq org-export-latex-listings 'minted
> '(("frame" "lines")
> ("fontsize" "\\scriptsize")
> ("linenos" "")))
> If I test this with "emacs -Q", it works. If I test it with my default,
> code is exported as "verbatim". This suggests the bug is in an init file
> of mine.
> However, I have removed all Org sections of my init file. I am fairly
> confident this is not a setting of mine, since if I look at the current
> state included in a "org-submit-bug-report", the state is almost the
> same between "emacs" and "emacs -Q", the only difference being Org 7.9 v.
> Org 8.6, and a few default settings that have changed between the two.
The new exporter, which arrived in 8.0, renamed most variables related
to export. I think the variables you are setting here are now named:
My guess is that renaming them in your init file will fix the problem.
prev parent reply other threads:[~2014-04-29 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 14:53 minted in Org 8.6 Ken Mankoff
2014-04-29 15:43 ` Richard Lawrence [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).