From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: New beamer support
Date: Wed, 6 Jan 2010 18:33:25 +0100 [thread overview]
Message-ID: <D2FEBF81-7B5D-453B-A06D-C0B78D4A883C@gmail.com> (raw)
In-Reply-To: <87iqbfcifr.fsf@mundaneum.com>
On Jan 6, 2010, at 5:22 PM, Sébastien Vauban wrote:
> Hi Carsten,
>
> Carsten Dominik wrote:
>> there is now a new option org-beamer-frame-default-options
>
> When setting it into Emacs, great, it DOES WORK as expected!
>
> Though, I believe this is more a setting of the document itself,
> instead of
> one customization in my own `.emacs' file.
>
> I would rather like my colleagues to get the same output when
> compiling my
> document. I tried, then, the following:
>
> --8<---------------cut here---------------start------------->8---
> * COMMENT Setup
>
> # This is for the sake of Emacs.
> # Local Variables:
> # ispell-local-dictionary: "en_US"
> # org-beamer-frame-default-options: "[allowframebreaks]"
> # End:
> --8<---------------cut here---------------end--------------->8---
>
> with no success, though.
>
> Maybe I would have to try with a `#+BIND'.
#+BIND will do the trick, it was made just for this.
> Though, wouldn't it be better to
> explicitly add something like:
>
> --8<---------------cut here---------------start------------->8---
> #+BEAMER_FRAME_EXTRA_OPTIONS: [allowframebreaks]
> --8<---------------cut here---------------end--------------->8---
Yes, that would make sense if it is a frequently used feature.
I like to hesitate with introducing these special customizations
until I am convinced that this is used reasonably often. Otherwise
I would have to have 1000 of the special lines, approximately.
Question to all: How likely is the use of a default option you'd
want to have on *every* frame?
- Carsten
next prev parent reply other threads:[~2010-01-06 21:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 9:46 New beamer support Sébastien Vauban
2010-01-06 10:06 ` Carsten Dominik
2010-01-06 10:59 ` Sébastien Vauban
2010-01-06 12:36 ` Carsten Dominik
2010-01-06 13:35 ` Sébastien Vauban
2010-01-06 14:23 ` Carsten Dominik
2010-01-06 14:31 ` Carsten Dominik
2010-01-06 15:35 ` Sébastien Vauban
2010-01-06 17:32 ` Carsten Dominik
2010-01-06 15:47 ` Sébastien Vauban
2010-01-06 17:34 ` Carsten Dominik
2010-01-07 9:38 ` Sébastien Vauban
2010-01-07 10:35 ` Carsten Dominik
2010-01-07 10:56 ` Sébastien Vauban
2010-01-06 11:13 ` Christian Lasarczyk
2010-01-06 11:57 ` Carsten Dominik
2010-01-06 13:06 ` Sébastien Vauban
2010-01-06 11:40 ` Eric S Fraga
2010-01-06 13:03 ` Sébastien Vauban
2010-01-06 13:25 ` Carsten Dominik
2010-01-06 16:22 ` Sébastien Vauban
2010-01-06 17:33 ` Carsten Dominik [this message]
2010-01-07 8:41 ` Sébastien Vauban
2010-01-07 14:39 ` Darlan Cavalcante Moreira
2010-01-07 15:43 ` Carsten Dominik
2010-01-07 16:16 ` Sébastien Vauban
2010-01-07 18:03 ` Darlan Cavalcante Moreira
2010-01-07 18:18 ` Carsten Dominik
2010-01-07 19:24 ` Sébastien Vauban
2010-01-07 16:48 ` Carsten Dominik
2010-01-07 8:54 ` Sébastien Vauban
2010-01-07 9:26 ` Carsten Dominik
2010-01-07 9:47 ` Sébastien Vauban
2010-01-07 10:00 ` Carsten Dominik
2010-01-07 10:21 ` Sébastien Vauban
2010-01-07 10:33 ` Carsten Dominik
2010-01-07 11:23 ` Sébastien Vauban
2010-01-07 11:30 ` [beamer] Order in preamble Sébastien Vauban
2010-01-07 13:15 ` Carsten Dominik
2010-01-07 15:54 ` Sébastien Vauban
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=D2FEBF81-7B5D-453B-A06D-C0B78D4A883C@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).