From: Jay Snoddy <jaysnoddy@gmail.com>
To: emacs-orgmode@gnu.org
Subject: latex export: using levels to export to beamer and article-only mode (with beamerarticle)
Date: Tue, 19 Oct 2010 12:03:49 -0400 [thread overview]
Message-ID: <4CBDC165.4030504@gmail.com> (raw)
I am attempting to make a presentation and lecture notes out of org,
similar to what I have done before in normal latex.
I would like to use the heading levels to determine what does or does
not get displayed in presentation mode. The very lowest levels would be
seen only in lecture notes; the latter might be extensive text.
(Note that the lecture notes are to be in the latex class, article, with
\beamerarticle.... Not as the beamer "notes" per se . Beamer allows for
"modes" to hide article content from slides)
I am an org mode and emacs newbie and seem to be making newbie mistakes
in approach, though, so I would like to ask for ideas on the "best"
approach for this.
I would like to do something like the following...
* section
** subsection
*** frame (but possibly subsubsection in article mode.)
**** one (and only one) item within an itemized list environment
***** \only<article>{ \paragraph{%s}}
****** \only<article>{ \subparagraph{%s}}
******* \only<article>{%s}
******** \only<article>{%s}
I would like to avoid blocks or labels for this and just determine this
by heading level, as --at least in my newbie hands-- moving things
around when writing/revising is a lot simpler if I just stick with
simple outlining.
For the subset of work involving lecture notes, I would be willing to
lose ability to change frame levels.
I am using a day old Org version.
Any thoughts or suggestions would be very much appreciated!
next reply other threads:[~2010-10-19 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 16:03 Jay Snoddy [this message]
2010-10-21 1:31 ` latex export: using levels to export to beamer and article-only mode (with beamerarticle) Mark Elston
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CBDC165.4030504@gmail.com \
--to=jaysnoddy@gmail.com \
--cc=emacs-orgmode@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.