emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Christoph LANGE <math.semantic.web@gmail.com>
Cc: Orgmode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: [export] Beamer frames containing lstlisting are no longer made fragile
Date: Sat, 14 Sep 2013 16:33:25 +0200	[thread overview]
Message-ID: <877gej4gne.fsf@gmail.com> (raw)
In-Reply-To: <52346F37.3010803@gmail.com> (Christoph LANGE's message of "Sat, 14 Sep 2013 16:14:15 +0200")

Hello,

Christoph LANGE <math.semantic.web@gmail.com> writes:

> Still I think the following sentence in the documentation (section 12.5)
> is easy to misunderstand:
>
> "`fragile' option is added automatically if it contains source code that
> uses any verbatim environment".

What would you suggest instead?

> I think it means that when I use a proper "source block" using
> #+BEGIN_SRC, the exporter automatically sets the [fragile] option as
> needed.

It isn't just about source blocks, see `org-beamer-verbatim-elements'.

> Anyway, you told me how to make my legacy {lstlisting} environments
> work.  Is this approach, of manually setting "BEAMER_OPT: fragile" the
> preferred way whenever you have a listing in a non-standard language,
> where the {lstlisting} environment requires special arguments (e.g.
> "morekeywords")?  Or is there some way of passing extra arguments into
> the {lstlisting} environment that is created from #+BEGIN_SRC?

At the moment, the only way to pass extra arguments to lstlisting is
using `org-latex-listings-options'. IOW, it isn't possible to set
specific options for a given block.

Though, it should be fairly easy to implement an :extra attribute for
source blocks. E.g.,

  #+attr_latex: :extra key1=val1,key2=val2
  #+begin_src
  ...
  #+end_src


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-09-14 14:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 12:53 [export] Beamer frames containing lstlisting are no longer made fragile Christoph LANGE
2013-09-13 15:32 ` Nicolas Goaziou
2013-09-14 14:14   ` Christoph LANGE
2013-09-14 14:33     ` Nicolas Goaziou [this message]
2013-10-05 14:20       ` Christoph LANGE
  -- strict thread matches above, loose matches on Subject: below --
2013-09-13 12:21 Christoph LANGE
2013-09-16  7:51 ` Eric S Fraga
2013-10-05 14:25   ` Christoph LANGE

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=877gej4gne.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=math.semantic.web@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).