Re: Beamer support - 2nd round

[Adam Spiers <orgmode@adamspiers.org>]

On Mon, Dec 14, 2009 at 09:11:49AM +0100, Carsten Dominik wrote:
> On Dec 10, 2009, at 10:32 PM, Adam Spiers wrote:
> >>2.2 Frames
> >>===========
> >>
> >>The BEAMER_FRAME_LEVEL setting governs which levels become frames.  If
> >>that option is set to 0, then frames are only created by setting the
> >>`BEAMER_env' property of an entry to the value `frame'.
> >>
> >>The heading of the entry will become the frame title.  If the frame
> >>title contains the string `\\', the line will be split at that
> >>location, and the second half will become the frame /subtitle/.  If
> >>you need a line break in the frame title, use `\newline' or
> >>`\linebreak'.
> >
> >If the frame title is long enough to require a line break, most likely
> >it will start creeping over the right-hand margin of the emacs frame
> >during editing.  Consequently anything which can save a few columns
> >might be helpful, so how about allowing \n to mean the same as
> >\newline ?
> 
> I am not sure I'd like this as a default, because the used of \n may
> be many including in source code examples

Hmm, it seems quite unlikely you'd need a literal \n in the frame
*title*, but it's possible I guess ...

> but why don't you just do this:
> 
> (defun my-make-backslash-n-mean-newline ()
>   (save-excursion
>     (goto-char (point-min))
>     (replace-regexp "\\\\n\\>" "\\\\newline")))
> (add-hook 'org-export-preprocess-hook
>           'my-make-backslash-n-mean-newline)

That's cool, thanks :-)  I don't have a strong need for this, but was
just suggesting it as an idea to help promote the legibility and ease
of entry of org-beamer source "code".

Thanks,
Adam