From: Carsten Dominik <carsten.dominik@gmail.com>
To: Darlan Cavalcante Moreira <darcamo@gmail.com>
Cc: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>, emacs-orgmode@gnu.org
Subject: Re: Re: New beamer support
Date: Thu, 7 Jan 2010 16:43:06 +0100 [thread overview]
Message-ID: <E96B5EC9-6384-411A-A2C0-D6755CE3F491@gmail.com> (raw)
In-Reply-To: <4b45f234.8702be0a.68d2.ffffd38c@mx.google.com>
On Jan 7, 2010, at 3:39 PM, Darlan Cavalcante Moreira wrote:
>
> I don't think org-mode should try to detect when to use any of the
> frame options
> in beamer. This could get into the way more then helping, specially
> the
> allowframebreaks option.
Do you also think I should not try to add the fragile option
automatically?
- Carsten
>
> In fact, the beamer manual tells you not to use the allowframebreaks
> option
> except for long bibliographies (well, it also tells you not to use
> long
> bibliographies) and I agree with this. In a presentation you have to
> choose
> carefully what you will put in each slide and always leaving this to
> beamer with
> the allowframebreaks is not a good approach.
>
> In addition, I agree that when working in a presentation with org-
> mode you
> compile much less, but you should still compile sometimes to see if
> the slides
> are well designed. I don't know if Carsten has plans to implement
> this, but a
> "fast preview" that exports and compiles only the current slide
> could be useful
> here.
>
> At last, I have a small feature request that would help organizing the
> information among the slides. Right now you can use Alt+up/down
> arrow to move a
> list item in a heading, but org does not allow passing beyond a
> heading
> limit. This makes sense in a normal org file and is very useful, but
> when
> writing a presentation with org this restriction can get into the
> way. This is
> not a big deal, but maybe others are also interested in this.
>
> - Darlan Cavalcante Moreira
>
> At Thu, 07 Jan 2010 09:41:29 +0100,
> Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:
>>
>> Hi Carsten,
>>
>> Carsten Dominik wrote:
>>> On Jan 6, 2010, at 5:22 PM, Sébastien Vauban wrote:
>>>> 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.
>>
>> #+BIND: org-beamer-frame-default-options "[allowframebreaks]"
>>
>> does work.
>>
>>
>>>> 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?
>>
>> The problem is similar to the `fragile' option. Either we can
>> detect the
>> "overflow" (and the automatically add the option only when needed),
>> or we must
>> add it everywhere in order to ensure we won't have text cut.
>>
>> It's a bit different from when we directly edit beamer files. We
>> compile often
>> and we see the problem appearing.
>>
>> Here, with Org, we would just work in Org only, and publish once at
>> the end. A
>> bit more easy to be aware that some text may have pass away.
>>
>> As #+BIND works, I can imagine living quite honestly the way it
>> currently is,
>> but I let the others decide upon this.
>>
>> Best regards,
>> Seb
>>
>> --
>> Sébastien Vauban
>>
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
next prev parent reply other threads:[~2010-01-07 15:43 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
2010-01-07 8:41 ` Sébastien Vauban
2010-01-07 14:39 ` Darlan Cavalcante Moreira
2010-01-07 15:43 ` Carsten Dominik [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E96B5EC9-6384-411A-A2C0-D6755CE3F491@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=darcamo@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.