From: James Harkins <jamshark70@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Beamer title is (incorrectly?) outside of a frame
Date: Mon, 23 Dec 2013 11:33:24 +0800 [thread overview]
Message-ID: <a28f4d3d-fd16-4ec1-a67d-c2c958e9f821@dewdrop-world.net> (raw)
In-Reply-To: <871u15j9ct.fsf@gmail.com>
On Sunday, December 22, 2013 9:36:34 PM HKT, Nicolas Goaziou wrote:
>> Oh, I think I see the issue... there's only one org-latex-title-command.
>>
>> ;; 10. Title command.
>> (org-element-normalize-string
>> (cond ((string= "" title) nil)
>> ((not (stringp org-latex-title-command)) nil)
> ...
>
> I don't think the variable is problematic as you can wrap a frame around
> it. Anyway, patch welcome.
Sure, I can work on a patch. I'll need this in another month or so.
One question, though: How would I determine the LaTeX document class
programmatically?
"Beamerarticle" uses the article class, with \usepackage{beamerarticle} in
the preamble. This package redefines beamer commands so that they print
somewhat reasonably well in article format. So, org needs to generate
beamer-style commands, and that's done by the beamer backend.
That is:
Exporting as presentation (normal)
- Backend = beamer
- Document class = beamer
Exporting as article
- Backend = beamer
- Document class = article
In the former case, the title command should be wrapped in a frame. In the
latter, it should not.
Currently, I'm working around it by #+bind'ing org-latex-title-command, but
I'd like that to be automatic.
hjh
next prev parent reply other threads:[~2013-12-23 3:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 10:38 Beamer title is (incorrectly?) outside of a frame James Harkins
2013-12-22 10:42 ` James Harkins
2013-12-22 13:36 ` Nicolas Goaziou
2013-12-23 3:33 ` James Harkins [this message]
2013-12-23 8:25 ` Nicolas Goaziou
2013-12-26 5:50 ` James Harkins
[not found] ` <bc14736f-f98c-4112-8f54-b35dcb5416a9@dewdrop-world.net>
2014-01-11 6:39 ` James Harkins
2014-01-11 8:44 ` Nicolas Goaziou
2014-01-11 8:49 ` 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=a28f4d3d-fd16-4ec1-a67d-c2c958e9f821@dewdrop-world.net \
--to=jamshark70@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).