all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Masterson <dsmasterson92630@outlook.com>
To: Naresh Gurbuxani <naresh_gurbuxani@hotmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Orgmode and Beamer
Date: Mon, 28 Oct 2024 17:47:03 -0700	[thread overview]
Message-ID: <LV8P223MB092012472CA25371C36AB0F49B4B2@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <IA1P223MB0499EAB9934E0C44F94AFCCEFA4A2@IA1P223MB0499.NAMP223.PROD.OUTLOOK.COM>

Ok.  Can that be done based upon which export engine you choose -- 
ox-latex or ox-beamer?  Example?

On 10/28/24 16:57, Naresh Gurbuxani wrote:
>   Comment out one of these:
>
> #+latex_class: article
> #+latex_class: beamer
>
>
> Sent from my iPhone
>
>> On Oct 28, 2024, at 6:32 PM, David Masterson <dsmasterson92630@outlook.com> wrote:
>>
>> Does anyone have a recommendation on how to structure an Org document such that it can be exported to either Latex or Beamer? Suppose you have a (small) thesis that you are writing and you want to generate Beamer slides of a high-level view of the document, but also generate a PDF for the whole document.   I suppose you could break it into two files, but then you'd have to copy (certain) changes from file to file.  I was wondering if it could be done with one file such that updates to the master document are simultaneously reflected in the Beamer slides.  Is this going to involve liberal use of #+BEGIN...#+END blocks?
>>
>> David Masterson
>>
>>


  reply	other threads:[~2024-10-29  0:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 22:27 Orgmode and Beamer David Masterson
2024-10-28 23:57 ` Naresh Gurbuxani
2024-10-29  0:47   ` David Masterson [this message]
2024-10-29  2:05 ` Leo Butler
2024-10-29  3:38   ` David Masterson

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=LV8P223MB092012472CA25371C36AB0F49B4B2@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM \
    --to=dsmasterson92630@outlook.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=naresh_gurbuxani@hotmail.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 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.