From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Org file to generate both beamer and standard LaTeX file
Date: Thu, 4 Jul 2013 00:22:00 +0200 [thread overview]
Message-ID: <20130703222200.GA3051@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <87sizv9vog.fsf@free.fr>
Hi,
On Wed, Jul 03, 2013 at 11:32:15PM +0200, Julien Cubizolles wrote:
> I've been an newbie org user for a while now: in particular, I've never
> played with export much and all my LaTeX work as been done with AucTeX
> in a .tex file. I'm considering switching to an Org-based setup if I
> could get the following, mainly for courses I'm preparing for which I
> would need beamer / handouts / normal LaTeX / maybe odt export
>
> * sectioning (\section et al commands in LaTeX) done with first and
> second/third level heading, common to all exporters
>
> * some common LaTeX code for all exports (definitions/theorems)
>
> * manual specification of individual frames for the Beamer export. I
> guess I would need LaTeX blocks for that, would AucTeX be available in
> the edit buffer ?
>
> * manual LaTeX code for normal LaTeX
>
> * some python/pgfplots/tikz source blocks generating images, used in the
> different export modes.
>
> Can it be done ? Even better, did one of you already implemented
> something similar ?
All of what you list above is supported. You just need to learn the
syntax. To get started please look at the ox-beamer tutorial on Worg.
It is a little outdated by now, but it should provide a good starting
point for you. And of course all the features are very nicely
documented in the manual, take a look there.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-07-03 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 21:32 Org file to generate both beamer and standard LaTeX file Julien Cubizolles
2013-07-03 22:22 ` Suvayu Ali [this message]
2013-07-04 20:46 ` Julien Cubizolles
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=20130703222200.GA3051@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@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 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).