emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: adding options to the minted environment of exported source blocks in latex
Date: Sun, 09 Feb 2014 11:16:05 +0100	[thread overview]
Message-ID: <m28utk4mmy.fsf@polytechnique.org> (raw)
In-Reply-To: <87lhxmzm78.fsf@gmail.com> (Nicolas Goaziou's message of "Fri, 07 Feb 2014 21:45:15 +0100")

Hi Nicolas,

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> At the moment, there is no Org way to add arbitrary options to listings
> or minted on a per block basis.
>
> There are basically two ways to implement this. Either we add
> an :options keyword and stuff options there:
>
>   #+attr_latex: :options a=b,c=d
>   #+begin_src ...
>
> Another option is to turn options into keywords:
>
>   #+attr_latex: :a b :c d
>   #+begin_src ...
>
> The latter is more elegant, but it requires to know about every
> minted/listings options.
>
> It is also possible to do something in-between, i.e., tell Org about
> a few selected keywords and stuff the others into :options. This is what
> is done for images. Org knows about :height and :width and uses :options
> for everything else.

The latter would be great. The option I'm considering does not exist in
minted, I add it in my preamble.

Best,

Alan

  reply	other threads:[~2014-02-09 10:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07 15:19 adding options to the minted environment of exported source blocks in latex Alan Schmitt
2014-02-07 20:45 ` Nicolas Goaziou
2014-02-09 10:16   ` Alan Schmitt [this message]
2014-02-10 16:51     ` Nicolas Goaziou
2014-02-11 15:23       ` Alan Schmitt
2014-02-11 18:10         ` Nicolas Goaziou
2014-02-12 10:25           ` Alan Schmitt
2014-03-25 15:04             ` Nicolas Goaziou
2014-03-25 15:48               ` Alan Schmitt
2014-03-25 18:10                 ` 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=m28utk4mmy.fsf@polytechnique.org \
    --to=alan.schmitt@polytechnique.org \
    --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).