From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: BEAMER_HEADER in `org-latex-classes'
Date: Fri, 08 Nov 2013 11:27:00 +0100 [thread overview]
Message-ID: <86ob5vfatn.fsf@somewhere.org> (raw)
In-Reply-To: 8738n79pj4.fsf@gmail.com
Hello,
Nicolas Goaziou wrote:
> "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org> writes:
>
>> I'd then propose the attached patch for the documentation.
>
> Thank you for the patch.
>
>> BTW, what's the difference between #+LATEX_HEADER and #+LATEX_HEADER_EXTRA
>> lines, if both end up under the same umbrella ([EXTRA])? Couldn't we suppress
>> the #+LATEX_HEADER_EXTRA keyword?
>
> According to section 12.7.2 in manual, LATEX_HEADER_EXTRA will not be
> loaded when previewing LaTeX snippets, unlike to LATEX_HEADER.
Shouldn't the similar principle be applied to BEAMER_HEADER, that is have a
BEAMER_HEADER_EXTRA keyword as well?
>> * ox-latex.el (org-latex-classes): Add BEAMER_HEADER in the
>> documentation string.
>
> `beamer' is a different back-end than `latex', or to put it differently,
> `latex' back-end is not supposed to know about `beamer'.
I understand.
> That's why no reference to `beamer' appears in `org-latex-classes'.
Though, this is only true as long as ox-beamer is not loaded. Because ox-beamer
does add "beamer" to `org-latex-classes' (which is right IMO).
> If documentation is needed, I think it should go in the manual, as
> a footnote close to the reference to BEAMER_HEADER.
OK.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-11-08 10:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 17:51 BEAMER_HEADER in `org-latex-classes' Sebastien Vauban
2013-11-07 20:22 ` Nicolas Goaziou
2013-11-08 9:40 ` Sebastien Vauban
2013-11-08 10:05 ` Nicolas Goaziou
2013-11-08 10:27 ` Sebastien Vauban [this message]
2013-11-08 10:57 ` Nicolas Goaziou
2013-11-08 11:19 ` Sebastien Vauban
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=86ob5vfatn.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).