From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [ANN] Beamer back-end for org-export in contrib/
Date: Wed, 4 Jul 2012 18:26:46 +0200 [thread overview]
Message-ID: <CAMXnza3_FMVG0X2KVhKi9ih8pC2c+U70VSAqt==PJs+2CihLRg@mail.gmail.com> (raw)
In-Reply-To: <87ehorfr0w.fsf@gmail.com>
Hi Nicolas,
On Wed, Jul 4, 2012 at 6:08 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>> The exported latex source however has the following:
>>
>> \documentclass[11pt]{article}
>
> This is because "LaTeX_CLASS" and "LaTeX_CLASS_OPTIONS" properties are
> not recognized as export properties. You have to use them as a buffer
> keyword (#+LATEX_CLASS: beamer).
>
Okay, but this brings up a use case issue for me. I usually have a org
file dedicated to a project I'm working on. Then I have notes on
different sub topics and presentations in different subtrees. As needed,
I export the subtrees. This can be simple LaTeX or html export for notes
(to share or print), or beamer export in case I want to give a
presentation.
If I understand correctly, having a buffer keyword would mean I would
need to find and update it appropriately everytime I want to export
something. I can live with this, but it would be great if there was
support these export options as properties. Then all the subtree exports
can be decoupled easily.
>> I would also like to work on some user documentation for the beamer
>> backend (when I do find some free time :-p). I see that org-e-beamer.el
>> is very well commented so I will start there, but do you have any other
>> pointers that might help me clearly document the supported features?
>
> I suppose you know about Eric S Fraga's tutorial at:
>
> http://orgmode.org/worg/org-tutorials/org-beamer/tutorial.html
>
> Since the back-end shares a lot with its previous incarnation, you will
> find, /mutatis mutandis/, much information about it.
Okay thanks, I was also thinking something similar and started based on
that. For all the common features I'll refer to Eric's tutorial and will
outline only the new, altered or deprecated features in my file.
Thanks again for this beautiful work. :)
Cheers,
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2012-07-04 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 14:59 [ANN] Beamer back-end for org-export in contrib/ Nicolas Goaziou
2012-06-30 18:46 ` suvayu ali
2012-07-02 12:22 ` Nicolas Goaziou
2012-07-04 1:30 ` suvayu ali
2012-07-04 16:08 ` Nicolas Goaziou
2012-07-04 16:26 ` suvayu ali [this message]
2012-07-05 11:56 ` Nicolas Goaziou
2012-07-07 10:04 ` suvayu ali
2012-07-07 12:32 ` Nicolas Goaziou
2012-07-07 12:56 ` suvayu ali
2012-07-07 12:58 ` Nicolas Goaziou
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='CAMXnza3_FMVG0X2KVhKi9ih8pC2c+U70VSAqt==PJs+2CihLRg@mail.gmail.com' \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).