emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Jason Dunsmore <jason.public@gmail.com>
Cc: Matt Lundin <mdl@imapmail.org>, emacs-orgmode@gnu.org
Subject: Re: Re: org-beamer bug
Date: Fri, 26 Mar 2010 08:30:52 +0100	[thread overview]
Message-ID: <F575B582-F45A-4DF9-A6B3-8CB28BAB5F0F@gmail.com> (raw)
In-Reply-To: <87aatw5fzi.fsf@riotblast.dunsmor.com>


On Mar 25, 2010, at 9:00 PM, Jason Dunsmore wrote:

> Thanks for the explanation.
>
> The documentation is confusing.
>
>> If this property is set, the entry will also get a `:B_environment:'
>> tag to make this visible.  This tag has no semantic meaning, it is
>> only a visual aid.
>
> I thought there was actually a `:B_environment:' tag.  I also didn't
> know that this was referring to auto-selecting the tag when using the
> PROPERTIES selection interface (C-c C-c inside a PROPERTIES drawer).
>
> For that part of the documentation, I would suggest:
>
> ``If this property is set using C-c C-c inside the properties drawer,
>  the entry will also get an environment tag (eg. :B_block:) to make
>  this visible. This tag has no semantic meaning, it is only a visual
>  aid.''
>
> The org-beamer-set-environment-tag docstring states:
>
> ``Set an environment tag, to determine the beamer environment to be  
> used.
>  This makes use of the fast tag selection interface.''
>
> But it doesn't determine the beamer environment to be used.  I would
> suggest instead:
>
> ``Set a beamer environment tag using the fast tag selection interface.
>  This is only a visual aid to indicate the beamer environment
>  configured in the :BEAMER_env: property.''
>
> What is the point of having an interface to select the beamer
> environment tags (C-c C-b) if they are auto-generated?

Hi Jason,  the documentation is indeed not very clear on this, also  
because the background is confusing:

1. Only the property counts, the tag is visual and has no semantic  
meaning
2. I am using a property because all the other beamer stuff is also  
properties
3. To make selecting the correct environment very convenient and fast,
    I am using a special version of the tag interface which will  
change both
    the tag and the property value.

I'll see if I can make the documentation clearer here. In fact, even  
the function
name org-beamer-set-environment-tag is bad, and I have just changed it  
to org-beamer-select-environment'.

While this does improve the documentation, I still think that more  
extensive documentation, examples and tutorial for the beamer support  
would be very good to have on Worg, and I have not lost hope that  
someone will pick up this task.

>
> Also, the example from
> http://orgmode.org/manual/Beamer-class-export.html shows a :B_block:  
> tag
> in use without the :BEAMER_env: property.
>
> --8<---------------cut here---------------start------------->8---
>     ***  
> Request                                                   :B_block:
>         Please test this stuff!
> --8<---------------cut here---------------end--------------->8---
>
> This should be:
>
> --8<---------------cut here---------------start------------->8---
>     ***  
> Request                                                   :B_block:
>         :PROPERTIES:
>         :BEAMER_env: block
>         :END:
>         Please test this stuff!
> --8<---------------cut here---------------end--------------->8---

Indeed, thanks for catching this documentation bug.

>
> Did org-beamer previously support configuring beamer environments via
> tags?

Yes, for a short time

>  If so, why was it removed?  It seems like a nice feature.

Because we added much more functionality, all of which was using  
properties.

Regards

- Carsten

      reply	other threads:[~2010-03-26  7:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 15:55 org-beamer bug Jason Dunsmore
2010-03-25 17:18 ` Matt Lundin
2010-03-25 20:00   ` Jason Dunsmore
2010-03-26  7:30     ` Carsten Dominik [this message]

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=F575B582-F45A-4DF9-A6B3-8CB28BAB5F0F@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jason.public@gmail.com \
    --cc=mdl@imapmail.org \
    /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).