From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Fraga Subject: Re: [beamer] When are :BEAMER_envargs: used or ignored? Date: Thu, 26 Apr 2012 17:44:56 +0930 Message-ID: <87ehranc3j.fsf@ucl.ac.uk> References: <87ehtgoita.wl%jamshark70@dewdrop-world.net> <87sjfsmnhs.fsf@ucl.ac.uk> <874ns89l81.wl%jamshark70@dewdrop-world.net> <87397s9dss.wl%jamshark70@dewdrop-world.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:46748) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SNJrG-0006hd-IE for emacs-orgmode@gnu.org; Thu, 26 Apr 2012 04:15:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SNJrA-0002yb-B1 for emacs-orgmode@gnu.org; Thu, 26 Apr 2012 04:15:22 -0400 Received: from db3ehsobe001.messaging.microsoft.com ([213.199.154.139]:50530 helo=db3outboundpool.messaging.microsoft.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SNJrA-0002rB-0m for emacs-orgmode@gnu.org; Thu, 26 Apr 2012 04:15:16 -0400 In-Reply-To: <87397s9dss.wl%jamshark70@dewdrop-world.net> (James Harkins's message of "Wed, 25 Apr 2012 20:49:39 +0800") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: James Harkins Cc: emacs-orgmode@gnu.org James Harkins writes: > At Wed, 25 Apr 2012 18:09:18 +0800, > James Harkins wrote: >> > Whether it should be a feature request or not is debatable. The syntax >> > is, at present, fairly straightforward in that the headline text becomes > >> > the argument to the environment defined. >> >> I think "the headline text becomes the argument..." is the opposite of straightforward. :-) > > OK, wait, I get it: > > \begin{alertblock}{HEADLINE TEXT HERE} > > \begin{beamercolorbox}{HEADLINE TEXT HERE} > > OK, it's a consistent translation. Yes. > But I still have the issue with it > that the user has to adapt the org-file structure to suit beamer's > requirements. Org-mode is all about reflecting the content in a way > that makes sense FIRST to humans, and only secondarily to exporting > engines. I agree. However, the problems arise when exporting because of fundamentally different structures between org and the export target. This is why we have the various kludges (if people can forgive me for calling them this) like ATTR_HTML and ATTR_LATEX. There is no easy or elegant mechanism in org for satisfying all the different export target requirements that are fundamentally inconsistent with org's outline heritage. For this particular case, it could be that the beamercolorbox environment could be made to expect a specific PROPERTY, much like the column environment does. The question would then be: what should the headline be used for as beamercolorbox has no real text content argument. I would guess that if you could suggest a consistent and more elegant solution, it would be considered favourably and maybe somebody would take it up and implement it. No promises, however! -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1 : using Org-mode version 7.8.06 (release_7.8.06.181.g67694.dirty)