emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mark Elston <m_elston@comcast.net>
To: emacs-orgmode@gnu.org
Subject: Re: latex export: using levels to export to beamer and article-only mode (with beamerarticle)
Date: Wed, 20 Oct 2010 18:31:37 -0700	[thread overview]
Message-ID: <4CBF97F9.8070502@comcast.net> (raw)
In-Reply-To: <4CBDC165.4030504@gmail.com>

Jay,

I do something similar but don't use beamer.  I have two sets of latex
output from my notes, one for handouts and one for lecture notes.  I
use an arrangement of sub-headings without titles but with tags for
describing what is included in each set of output.  It is all put
together with an SCons script to take the specific notes and generate
a PDF output for notes and handouts.

How this could be folded into a beamer presentation I am not sure.

If you would like details let me know and I can send you a
representative sample to play with.  It is kind of complicated,
unfortunately, since it also makes use of additional entries in
org-export-latex-classes, but since I have it working it meets
my needs.  YMMV.

Mark


On 10/19/2010 9:03 AM, Jay Snoddy wrote:
> 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!
>

      reply	other threads:[~2010-10-21  1:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 16:03 latex export: using levels to export to beamer and article-only mode (with beamerarticle) Jay Snoddy
2010-10-21  1:31 ` Mark Elston [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=4CBF97F9.8070502@comcast.net \
    --to=m_elston@comcast.net \
    --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 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).