From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Latex Export
Date: Sun, 02 Dec 2007 21:44:33 +0000 [thread overview]
Message-ID: <87d4tozs8u.fsf@bzg.ath.cx> (raw)
In-Reply-To: <20071202210405.GF4256@odin.demosthenes.org> (Russell Adams's message of "Sun, 2 Dec 2007 15:04:05 -0600")
Hi Russell,
Russell Adams <RLAdams@AdamsInfoServ.Com> writes:
> The exporters all refuse to export text before the first headline. I
> agree with that.
The exporters skip text before the first headline only if you set the
relevant option:
#+OPTIONS: skip:t
If you don't specify anything about this in the #+OPTIONS line, then the
exporters will fall back on `org-export-skip-text-before-1st-heading'.
This applies to normal text as well as text inside #+BEGIN_LaTeX and
#+END_LaTeX markers.
But this does not apply to text after #+TEXT though. This text is
*always* exported.
> However I'm including per buffer options at the top of my file,
> #+OPTIONS and the like. Turns out that #+BEGIN_LaTeX and #+END_LaTeX
> before the first headline are considered comments and not exported.
>
> This is a problem where I'm trying to select a style or define
> variables used later in LaTeX code.
I think the right way to do this is to set a local value for the
variable `org-export-latex-append-header' at the end of your file:
,----
| * COMMENT LaTeX local variable
|
| # Local Variables:
| # org-export-latex-append-header: "\\usepackage{fancyhrd}"
| # End:
`----
This will append "\usepackage{fancyhrd}" to the LaTeX header that is
defined in `org-export-latex-classes'.
> I think that BEGIN/END latex should be considered configuration data
> like other /^#/ directives and exported before the first headline.
>
> Comments?
#+BEGIN_LaTeX and #+END_LaTeX have a more general purpose than just
adding "configuration" and you should be able to use them anywhere
in the Org source.
I think the real question is: what people are doing of #+TEXT?
Is it useful as it is now ("this text comes before the first heading,
overriding the skip option")? Or should it be redefined so as to mean
"This piece of text should be inserted in the *header* of the target
format?"
Comment?
--
Bastien
next prev parent reply other threads:[~2007-12-02 21:56 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 3:15 Latex Export Russell Adams
2007-11-30 6:21 ` Giovanni Ridolfi
2007-11-30 7:27 ` Russell Adams
2007-11-30 12:40 ` Bastien
2007-12-01 7:14 ` Russell Adams
2007-12-02 21:04 ` Russell Adams
2007-12-02 21:44 ` Bastien [this message]
2007-12-21 22:36 ` Russell Adams
2007-12-21 23:33 ` Bastien
2008-01-09 20:53 ` Russell Adams
2008-01-15 11:26 ` Carsten Dominik
-- strict thread matches above, loose matches on Subject: below --
2017-08-10 2:01 LaTeX Export Scott Randby
2017-08-10 15:35 ` Richard Lawrence
2017-08-10 16:03 ` Scott Randby
2011-12-31 0:35 LaTeX export York Zhao
2011-12-31 8:09 ` Bastien
2011-12-31 18:07 ` York Zhao
2011-12-31 23:37 ` Steve Hafner
2012-01-01 19:52 ` York Zhao
2010-10-16 18:53 Re: Re: Re: Latex Export chris.m.malone
2010-10-16 19:14 ` Thomas S. Dye
2010-10-16 18:10 chris.m.malone
2010-10-16 18:40 ` Thomas S. Dye
[not found] <Pine.LNX.4.63.1010161331001.7948@scotty.ess.sunysb.edu>
2010-10-16 17:34 ` chris.m.malone
2010-10-16 17:54 ` Nick Dokos
2010-10-16 14:55 Chris Malone
2010-10-16 21:18 ` Scot Becker
2009-01-05 12:42 LaTeX Export Rasmus Pank Roulund
2009-01-05 15:29 ` Carsten Dominik
2009-01-05 16:10 ` Rasmus Pank Roulund
2009-01-06 12:00 ` Carsten Dominik
2009-01-08 17:48 ` Rasmus Pank Roulund
2009-01-08 21:38 ` Carsten Dominik
2009-02-10 20:46 ` Rasmus Pank Roulund
2009-02-11 10:34 ` Carsten Dominik
2009-02-11 15:56 ` Bernt Hansen
2009-02-11 16:08 ` Carsten Dominik
2009-02-12 18:25 ` Rasmus Pank Roulund
2009-01-05 15:43 ` Matthew Lundin
2008-12-21 23:12 Latex Export Flávio de Souza
2008-12-22 6:33 ` Carsten Dominik
2008-12-22 8:58 ` Flávio de Souza
2008-10-01 11:16 latex export Johanna Matschke
2008-10-01 12:15 ` Russell Adams
2008-10-10 21:13 ` Carsten Dominik
2007-11-02 10:11 LaTeX export Daniel Dehennin
2007-11-02 15:13 ` Bastien
2007-11-02 15:28 ` Daniel Dehennin
2007-11-02 16:05 ` Xiao-Yong Jin
2007-11-02 19:04 ` Bastien
2007-11-02 18:56 ` Bastien
2007-11-02 9:30 Daniel Dehennin
2007-09-28 7:19 Latex Export D. Kapetanakis
2007-09-29 13:23 ` Bastien
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=87d4tozs8u.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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).