Re: [Orgmode] Beamer support - 2nd round

[Carsten Dominik]

On Dec 10, 2009, at 10:32 PM, Adam Spiers wrote:

> On Thu, Dec 03, 2009 at 05:10:44PM +0100, Carsten Dominik wrote:
> > Dear all,
> >
> > after carefully listening to all your comments and thinking
> > things through more thoroughly, here is now my second attempt
> > to define beamer support in Org-mode.
>
> [snipped]
>
> This is very exciting :-)  Just one comment for now:
>
> > 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 ?

Hi Adam,

I am not sure I'd like this as a default, because the used of \n may  
be many including in source code examples, 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)


HTH

- Carsten