From: Josiah Schwab <jschwab@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Modifying the Beamer Exporter
Date: Fri, 28 Jun 2013 13:53:33 -0700 [thread overview]
Message-ID: <87r4fmvtwy.fsf@gmail.com> (raw)
In-Reply-To: <87vc4ygfhy.fsf@ucl.ac.uk>
> Maybe, maybe not. Difficult to say unless you give us a better idea of
> what kind of changes you plan on making.
I'm a little hazy, partially because my ideas seem to change quickly as
I learn more.
One of the more ambitious things that I'd like to do is to be able to
associate BibTeX references with a headlines in a way such that they are
collected at the level of the frame-headline and then rendered uniformly
in the page footers.
> In general, I find it sufficient to add a little bit of LaTeX code to my
> org files for most customisations or beamer specific commands. The
> great thing about org is that it is easy to write LaTeX directly when
> you need it. It's only if you wish to address different export targets
> that things become more complicated, but that's not what you are doing.
> Maybe gives us some idea of what it is you cannot do with ox-beamer and
> we can suggest whether what you intend to do is reasonable or not.
At least so far, it's no so much a question of "can't", as a matter of
style.
#+AUTHOR: Josiah \\ \small with Alice & Bob
vs
#+AUTHOR: Josiah
#+COLLABORATORS: Alice & Bob
Another example would be the use of a subtitle.
#+LATEX_HEADER: \subtitle{An Illustrative Example}
vs
#+SUBTITLE: An Illustrative Example
I have a preference for the "cleaner" version and wanted to implement it
in a way that it likely to age well as org development progresses.
Best,
Josiah
next prev parent reply other threads:[~2013-06-28 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 19:15 Modifying the Beamer Exporter Josiah Schwab
2013-06-28 20:14 ` Eric S Fraga
2013-06-28 20:53 ` Josiah Schwab [this message]
2013-06-29 13:48 ` Rasmus
2013-06-30 23:15 ` Josiah Schwab
2013-07-01 9:13 ` Rasmus
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=87r4fmvtwy.fsf@gmail.com \
--to=jschwab@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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.