From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph LANGE Subject: Re: [export] Beamer frames containing lstlisting are no longer made fragile Date: Sat, 14 Sep 2013 16:14:15 +0200 Message-ID: <52346F37.3010803@gmail.com> References: <52330AAE.9070000@gmail.com> <87r4csohz9.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36337) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VKqc1-0007hb-D7 for emacs-orgmode@gnu.org; Sat, 14 Sep 2013 10:14:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VKqbv-0005Pu-GP for emacs-orgmode@gnu.org; Sat, 14 Sep 2013 10:14:13 -0400 Received: from mail-ee0-x22d.google.com ([2a00:1450:4013:c00::22d]:37854) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VKqbv-0005Pj-8O for emacs-orgmode@gnu.org; Sat, 14 Sep 2013 10:14:07 -0400 Received: by mail-ee0-f45.google.com with SMTP id c50so1123347eek.18 for ; Sat, 14 Sep 2013 07:14:06 -0700 (PDT) In-Reply-To: <87r4csohz9.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: Orgmode Mailing List Hi Nicolas, 2013-09-13 17:32 Nicolas Goaziou: > If you're inserting the environment manually, Beamer export back-end > will not be able to detect that a "fragile" option is required. In that > case, you can also insert that option manually, by setting BEAMER_OPT > property to fragile in the headline representing your frame: > > * My frame > :PROPERTIES: > :BEAMER_OPT: fragile > :END: Thanks, that works – indeed I should have tried this first, as the documentation actually mentions it. 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". I think it means that when I use a proper "source block" using #+BEGIN_SRC, the exporter automatically sets the [fragile] option as needed. However the sentence could also be interpreted as reflecting the behaviour of the old exporter, which indeed scanned the full _LaTeX_ source code (e.g. in #+BEGIN_LaTeX) for certain environments and then set the [fragile] option. 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? Cheers, and thanks in advance, Christoph -- Christoph Lange, School of Computer Science, University of Birmingham http://cs.bham.ac.uk/~langec/, Skype duke4701 → Mathematics in Computer Science Special Issue on “Enabling Domain Experts to use Formalised Reasoning”; submission until 31 October. http://cs.bham.ac.uk/research/projects/formare/pubs/mcs-doform/