From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Spiers Subject: Re: Beamer support - 2nd round Date: Fri, 18 Dec 2009 11:12:05 +0000 Message-ID: <20091218111205.GF5666@atlantic.linksys.moosehall> References: <20091210213239.GC5666@atlantic.linksys.moosehall> Reply-To: Adam Spiers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NLal4-0003H0-Vo for emacs-orgmode@gnu.org; Fri, 18 Dec 2009 06:12:31 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NLakz-0003DH-Ek for emacs-orgmode@gnu.org; Fri, 18 Dec 2009 06:12:29 -0500 Received: from [199.232.76.173] (port=49949 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NLaky-0003Ct-MD for emacs-orgmode@gnu.org; Fri, 18 Dec 2009 06:12:24 -0500 Received: from vpn.id2.novell.com ([195.33.99.129]:35715 helo=gwia-smtp.id2.novell.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NLaky-00058R-5e for emacs-orgmode@gnu.org; Fri, 18 Dec 2009 06:12:24 -0500 Content-Disposition: inline In-Reply-To: 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@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.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