From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Problem with commented LaTeX header lines
Date: Thu, 02 Aug 2012 19:50:37 +0200 [thread overview]
Message-ID: <87y5lx6v4i.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87a9ydpbh6.fsf@gnu.org
Hi Bastien,
thanks for looking into this!
>
> Please always tell what exporter you are using.
>
I did mention this:
> > Test with new exporter - no cmbright:
^^^^^^^^^^^^^^^
I am sorry, if this was not explicit enough. (Is "new exporter" the
correct name?)
> Your example works with the default LaTeX exporter.
>
> With the new exporter, you don't get \usepackage{cmbright} because
> you explicitely asked not to export this subtree with :noexport:.
>
I do not agree, because it works as expected, if I remove the comment
sign:
,----
| #+TITLE: Commented LaTeX headers
|
|
| * Try to export this subtree
| With some text.
|
| And a second paragraph.
|
|
| ** And a section
| With some text.
|
| * Options :noexport:
| ** LaTeX Options
| #+LATEX_HEADER: \usepackage{hyperref}
| #+LATEX_HEADER: \usepackage{tikz}
| #+LATEX_HEADER: \usepackage{cmbright}
`----
> To me the new exporter is right here.
To me loosing that possibility would be hard, as my latex_header
sections tend to grow really long, so that I would not
be happy to move them to the top. This has always been one of the
really nice things in my opinion, that I can hide all this technical
information in a non-exported subtree.
Regards,
Andreas
next prev parent reply other threads:[~2012-08-02 17:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 9:32 Problem with commented LaTeX header lines Andreas Leha
2012-08-02 10:46 ` François Allisson
2012-08-02 15:20 ` Bastien
2012-08-02 17:50 ` Andreas Leha [this message]
2012-08-02 17:54 ` Nicolas Goaziou
2012-08-02 18:10 ` Andreas Leha
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=87y5lx6v4i.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--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).