emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernd Weiss <bernd.weiss@uni-koeln.de>
To: Eric S Fraga <e.fraga@ucl.ac.uk>, emacs-orgmode@gnu.org
Subject: Re: Customizing LaTeX-export, Beamer, \institute, and BEAMER_envargs
Date: Thu, 24 Mar 2011 06:34:24 -0400	[thread overview]
Message-ID: <4D8B1E30.5040606@uni-koeln.de> (raw)
In-Reply-To: <87oc50anev.fsf@ucl.ac.uk>

Am 24.03.2011 05:16, schrieb Eric S Fraga:
> Bernd Weiss<bernd.weiss@uni-koeln.de>  writes:
>
>> Dear all,
>>
>> I am preparing a Beamer presentation and I am having some trouble with
>> side effects (?) due to my attempt to customize the LaTeX-export. My
>> minimum example can be found below.
>>
>> The default LaTeX-export does not recognise the '\institute'-option (I
>> mean, as far as I know). For that reason, I run "(add-to-list
>> org-export-latex-classes ...)". Unfortunately, the export-function
>> does no longer recognice ":BEAMER_envargs: [plain]" (or
>> ":BEAMER_envargs: [shrink=5]")[1].
>
> yes, that is correct.  the default entry uses =org-beamer-sectioning=
> which is where headings are translated to latex section or frame or
> block etc entries *and* where the special beamer properties are
> processed.   As you have replaced the sectioning section of
> =org-export-latex-classes= with your own, you have lost all of that
> functionality.
>
> You seem to want to achieve two things:
>
> 1. added your macros into the latex preamble, and
> 2. add the [fragile] option to each frame.
>
> I would suggest you do 1 as you have done but keep org-beamer-sectioning
> as the second argument for the org-export-latex-classes entry.  To add
> [fragile] to each frame, I would recommend, instead, using some
> automated form of input, such as a yasnippet snippet like this one
> (untested):
>
> --8<---------------cut here---------------start------------->8---
> #name : frame
> # --
> ** ${1:frame title}
>     :PROPERTIES:
>     :BEAMER_envargs: ${2:[fragile]}
>     :END:
>     $0
> --8<---------------cut here---------------end--------------->8---
>
> so that typing "frame" followed by TAB would define a new headline,
> prompting for the title and possible arguments (with defaults).

Hi Eric,

Thanks for your help! Unfortunately, that's not what I was looking for 
and, therefore, rephrased my unclear question ("Specifying 
\institute[short]{long] in Beamer presentations"). As pointed out by 
Miklós or Suvayu, the solution was embarrassingly simpel: Just include

#+BEAMER_HEADER_EXTRA:  \institute{My insitute}

or

#+LaTeX_HEADER: \institute[short name]{My awesome institute}

Anyway, I really appreciate your help!

Bernd

  reply	other threads:[~2011-03-24 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-22 15:08 Customizing LaTeX-export, Beamer, \institute, and BEAMER_envargs Bernd Weiss
2011-03-24  9:16 ` Eric S Fraga
2011-03-24 10:34   ` Bernd Weiss [this message]
2011-03-24 10:57     ` Eric S Fraga

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=4D8B1E30.5040606@uni-koeln.de \
    --to=bernd.weiss@uni-koeln.de \
    --cc=e.fraga@ucl.ac.uk \
    --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).