emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Weylandt <michael.weylandt@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: PATCH -- allow user to set minted style
Date: Fri, 4 Apr 2014 15:32:55 -0400	[thread overview]
Message-ID: <FF1CCE69-DE08-41CA-85EA-56AD0C372B51@gmail.com> (raw)
In-Reply-To: <87d2gx7x14.fsf@gmail.com>



On Apr 4, 2014, at 14:46, Nicolas Goaziou <n.goaziou@gmail.com> wrote:

> Hello,
> 
> Michael Weylandt <michael.weylandt@gmail.com> writes:
> 
>> This requires a different mechanism than org-latex-minted-options
>> since it's a global/preamble option.
> 
> Since it's a global/preamble option, you can include it in your header,
> buffer wise, or with `org-latex-classes', or with
> `org-latex-packages-alist'...

Taking the choices in reverse:

- The minted style isn't passed as a package option so I'm not sure how org-latex-packages-alist helps.
 
- Yes, I have been putting it in the headers of my custom classes, but it has to follow \usepackage{minted} or I get a LaTeX error, so I wind up loading minted even when not using it. Having it as a variable also makes it easier to change the style. 

-I'm not sure what you mean by bufferwise

-Yes, #+LATEX_HEADER_EXTRA works but there's still the problem of failing if you don't use minted for that particular export.

I think the right analogy if with hyperref/hypersetup, which does have support of this style in Org. 

Michael

  reply	other threads:[~2014-04-04 19:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 15:11 PATCH -- allow user to set minted style Michael Weylandt
2014-04-04 18:46 ` Nicolas Goaziou
2014-04-04 19:32   ` Michael Weylandt [this message]
2014-04-04 20:24     ` Nicolas Goaziou
2014-04-04 21:15       ` Michael Weylandt
2014-04-05  7:42         ` Nicolas Goaziou

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=FF1CCE69-DE08-41CA-85EA-56AD0C372B51@gmail.com \
    --to=michael.weylandt@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@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).