emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Christoph LANGE <allegristas@gmail.com>
Cc: Orgmode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: [export] Beamer frames containing lstlisting are no longer made fragile
Date: Mon, 16 Sep 2013 08:51:48 +0100	[thread overview]
Message-ID: <874n9ldx0r.fsf@ucl.ac.uk> (raw)
In-Reply-To: <52330365.9090002@gmail.com> (Christoph LANGE's message of "Fri, 13 Sep 2013 14:21:57 +0200")

Christoph LANGE <allegristas@gmail.com> writes:

> Dear all,
>
> having created a number of Beamer presentations with the old exporter
> (Org version 7), I'm now working on the first Beamer presentation with
> the new exporter.
>
> Frames that contain an lstlisting environment are no longer made fragile
> automatically.  (Thus I'm not sure the documentation in manual section
> 12.5 "Beamer export" is still correct, which says "`fragile' option is
> added automatically if it contains source code that uses any verbatim
> environment".)
>
> My intuition after browsing the Org source code and documentation is
> that I should now use #+BEGIN_SRC and that then everything will be
> handled automatically.  However the language of my listings is a
> non-standard one, which requires a lot of custom options to the
> lstlisting environment.
>
> Could anyone kindly point me to an example?

I am not sure what it is you want an example of?  If it's how to
configure lstlisting for a new language, here are two examples:

#+latex_header: \lstdefinelanguage{gams}{
#+latex_header: keywords={all, positive, variable, variables, equation, equations, model,%
#+latex_header: minimizing, parameter, parameters, display, solve, using, /},
#+latex_header: sensitive=false,
#+latex_header: morecomment=[f]*,%
#+latex_header: morecomment=[s]{$ontext}{$offtext},
#+latex_header: morestring=[b]",
#+latex_header: morestring=[b]'
#+latex_header: }

#+latex_header: \lstdefinelanguage{Maxima}{
#+latex_header: keywords={addrow,addcol,zeromatrix,ident,augcoefmatrix,ratsubst,diff,ev,tex,%
#+latex_header: with_stdout,nouns,express,depends,load,submatrix,div,grad,curl,%
#+latex_header: rootscontract,solve,part,assume,sqrt,integrate,abs,inf,exp},
#+latex_header: sensitive=true,
#+latex_header: comment=[n]{/*}{*/}
#+latex_header: }

HTH,
eric
-- 
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.1.1-7-gaecdf5

  reply	other threads:[~2013-09-16  8:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 12:21 [export] Beamer frames containing lstlisting are no longer made fragile Christoph LANGE
2013-09-16  7:51 ` Eric S Fraga [this message]
2013-10-05 14:25   ` Christoph LANGE
  -- strict thread matches above, loose matches on Subject: below --
2013-09-13 12:53 Christoph LANGE
2013-09-13 15:32 ` Nicolas Goaziou
2013-09-14 14:14   ` Christoph LANGE
2013-09-14 14:33     ` Nicolas Goaziou
2013-10-05 14:20       ` 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=874n9ldx0r.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=allegristas@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).