From: Eric Fraga <e.fraga@ucl.ac.uk>
To: James Harkins <jamshark70@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [beamer] When are :BEAMER_envargs: used or ignored?
Date: Thu, 26 Apr 2012 17:44:56 +0930 [thread overview]
Message-ID: <87ehranc3j.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87397s9dss.wl%jamshark70@dewdrop-world.net> (James Harkins's message of "Wed, 25 Apr 2012 20:49:39 +0800")
James Harkins <jamshark70@gmail.com> 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)
next prev parent reply other threads:[~2012-04-26 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 7:07 [beamer] When are :BEAMER_envargs: used or ignored? James Harkins
2012-04-25 4:41 ` Eric Fraga
2012-04-25 10:09 ` James Harkins
2012-04-25 12:49 ` James Harkins
2012-04-26 8:14 ` Eric Fraga [this message]
2012-04-26 9:51 ` James Harkins
2012-04-26 11:15 ` Sebastien Vauban
2012-04-25 13:15 ` Eric Fraga
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ehranc3j.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=jamshark70@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).