From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?S=C3=A9bastien_Vauban?= Subject: Re: New beamer support Date: Thu, 07 Jan 2010 09:41:29 +0100 Message-ID: <87y6kab93a.fsf@mundaneum.com> References: <871vi3bm62.fsf@mundaneum.com> <87eim3zckf.wl%ucecesf@ucl.ac.uk> <87hbqzo05z.fsf@mundaneum.com> <87iqbfcifr.fsf@mundaneum.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Hi Carsten, Carsten Dominik wrote: > On Jan 6, 2010, at 5:22 PM, S=C3=A9bastien 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 m= ust 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 of= ten 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 i= s, but I let the others decide upon this. Best regards, Seb --=20 S=C3=A9bastien Vauban _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode-mXXj517/zsQ@public.gmane.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode