emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Jason Dunsmore <jason.public@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-beamer bug
Date: Thu, 25 Mar 2010 13:18:11 -0400	[thread overview]
Message-ID: <877hp0gw18.fsf@fastmail.fm> (raw)
In-Reply-To: <87eij85rbi.fsf@riotblast.dunsmor.com> (Jason Dunsmore's message of "Thu, 25 Mar 2010 10:55:29 -0500")

Hi Jason,

Jason Dunsmore <jason.public@gmail.com> writes:

> From reading the org-beamer documentation, I get the impression that the
> following two should headings should be equivalent:
>
>
> * Example 1                                                  :B_block:
>
> * Example 2
> :PROPERTIES:
> :BEAMER_env: block
> :END:
>
>
> However, only the second example is actually exported with a block
> environment.  This also happens with other environments.  The note
> environment is the only one I tested that works by using a tag.

According to the manual, the environment tags have no effect on the
export. They are simply visual aids. If org-beamer-mode is activated,
the tags are added automatically whenever you set the :BEAMER_env:
property.

,----
| `BEAMER_env'
|      The environment that should be used to format this entry.  Valid
|      environments are defined in the constant
|      `org-beamer-environments-default', and you can define more in
|      `org-beamer-environments-extra'.  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.
`----

Best,
Matt

  reply	other threads:[~2010-03-25 17:17 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 [this message]
2010-03-25 20:00   ` Jason Dunsmore
2010-03-26  7:30     ` Carsten Dominik

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=877hp0gw18.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jason.public@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).