emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <ucecesf@ucl.ac.uk>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Full list of org-beamer functionality?
Date: Sat, 04 Sep 2010 08:44:54 +0100	[thread overview]
Message-ID: <87bp8e54w9.wl%ucecesf@ucl.ac.uk> (raw)
In-Reply-To: <AANLkTi=W8JJcuYiHjr895Pu9Hmp0=S1La_SiGxR9ZmLJ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1981 bytes --]

On Fri, 3 Sep 2010 16:29:55 -0500, John Hendy <jw.hendy@gmail.com> wrote:
> 
> [1  <multipart/alternative (7bit)>]
> [1.1  <text/plain; ISO-8859-1 (7bit)>]
> Hi,
> 
> 
> When I've used beamer in the past for, say, blocks I just use:
> 
> \begin{block}
> Here is some text for the block
> \end{block}
> 
> I was looking more closely at this today:
> http://orgmode.org/worg/org-tutorials/org-beamer/tutorial.php
> 
> Is there a comprehensive list of all the beamer_env options that can be
> passed? For example since these work:
> BEAMER_env: block
> BEAMER_env: example
> 
> I would have figured that this would also work:
> BEAMER_env: alert
> 
> However only an itemized item shows up...
> 
> Also, example blocks are rendered with the block title: "Example (Heading
> title)" and I'd rather just have "Heading title" -- is there a way to do
> this?
> 
> It'd be great to see all of the possible property values that can be passed
> somewhere. Maybe something like the list at the bottom of the export options
> page in the org manual where you have a nice long list of all possible
> options in one place?

If you are using direct beamer support within org, by having

: #+startup: beamer

in the preamble of your file, you can use the C-c C-b sequence at any
heading to see all the possible options for that heading.  This
includes the example etc. blocks.

Regarding the output produced by beamer for the example block, this
has nothing to do with org: beamer has a number of different types of
blocks from a simple block through to examples, proofs, quotes,
definition etc.  Pick the right kind for what you want.  Also
choose the beamer theme that fits your needs.

> Lastly, is there an advantage to using properties if one doesn't anticipate
> using column view? If not perhaps I'll stick with straight LaTeX code...

Yes: being able to easily specify the type of block.  And it's about
hiding all the superfluous information, leaving only the text and
structure visible!

[-- Attachment #2: Type: text/plain, Size: 75 bytes --]

-- 
Eric S Fraga
GnuPG: 8F5C 279D 3907 E14A 5C29  570D C891 93D8 FFFC F67D

[-- Attachment #3: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-09-04  7:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03 21:29 Full list of org-beamer functionality? John Hendy
2010-09-04  7:44 ` Eric S Fraga [this message]
2010-09-04 16:17   ` John Hendy
     [not found]   ` <AANLkTimhwi_7z5NvFZFO0S=a2jx+kjPQjAkkbZ=aPkNc@mail.gmail.com>
2010-09-04 16:47     ` Eric S Fraga
2010-09-04 17:11       ` John Hendy

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=87bp8e54w9.wl%ucecesf@ucl.ac.uk \
    --to=ucecesf@ucl.ac.uk \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=jw.hendy@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).