From: torys.anderson@gmail.com (Tory S. Anderson)
To: Aaron Ecay <aaronecay@gmail.com>
Cc: orgmode list <emacs-orgmode@gnu.org>
Subject: Re: export for Beamer with author options
Date: Thu, 21 Aug 2014 17:46:21 -0400 [thread overview]
Message-ID: <87a96x4itu.fsf@gmail.com> (raw)
In-Reply-To: <87iollr1b2.fsf@gmail.com> (Aaron Ecay's message of "Thu, 21 Aug 2014 17:16:17 -0400")
Hey Aaron,
THat's a good idea but it doesn't quite work; looks like #+LATEX_HEADER stuff is put in BEFORE the author nil, so I just end up with \author{} to trump my author. I've tried rearranging things but it doesn't seem to effect it.
- Tory
Aaron Ecay <aaronecay@gmail.com> writes:
> Hi Tory,
>
> It looks like having a short and long author isn’t supported by the
> beamer exporter out of the box. Your best bet is probably to add this
> line to the top of your org file to turn off the automatic generation
> and insertion of \author by the export template:
>
> #+OPTIONS: author:nil
>
> Then, you can cause the appropriate line to be inserted in the export
> output with this line (also at the top of the file):
>
> #+LATEX_HEADER: \author[short-author]{Really \\long \\author}
>
> Whatever is on the latex header line will be inserted in the output
> verbatim, so you don’t need to (e.g.) add extra escaping to special
> characters like backslashes as you would if they were processed by org.
>
> Hope this is useful,
next prev parent reply other threads:[~2014-08-21 21:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 20:57 export for Beamer with author options Tory S. Anderson
2014-08-21 21:16 ` Aaron Ecay
2014-08-21 21:46 ` Tory S. Anderson [this message]
2014-08-21 22:17 ` Aaron Ecay
2014-08-22 12:08 ` Nicolas Goaziou
2014-08-22 13:08 ` Tory S. Anderson
2014-08-22 13:37 ` Nicolas Goaziou
2014-08-22 18:56 ` Marcin Borkowski
2014-08-22 19:23 ` Marcin Borkowski
2014-08-22 19:43 ` Aaron Ecay
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=87a96x4itu.fsf@gmail.com \
--to=torys.anderson@gmail.com \
--cc=aaronecay@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).