From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: comment section with latex_header
Date: Mon, 23 Mar 2015 11:01:25 +0100 [thread overview]
Message-ID: <874mpc6nii.fsf@gmx.us> (raw)
In-Reply-To: oluh9tcyv13.fsf@med.uni-goettingen.de
Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
> Hi Rasmus,
>
> Rasmus <rasmus@gmx.us> writes:
>> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>>
>>> Hi all,
>>>
>>> If there are `#+latex_header:' entries in a section and that section is
>>> `COMMENT'ed out, I'd expect the #+latex_header entries to be
>>> uneffective. As they are when I comment them out one by one as in
>>> `# #+latex_header:'.
>>>
>>> Is this a bug? (I'd say, yes....)
>>
>> Why? I guess you can still archive
>
> Could you expand on that?
Sorry, I must have clicked C-c C-c by accident.
#+LATEX_HEADERs in :noexport: sections are included. I guess that code in
COMMENT sections aren't included. So I guess keywords could also be
excluded. I don't know.
—Rasmus
--
⠠⠵
next prev parent reply other threads:[~2015-03-23 10:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 11:02 comment section with latex_header Andreas Leha
2015-03-22 11:37 ` Rasmus
2015-03-23 8:31 ` Andreas Leha
2015-03-23 10:01 ` Rasmus [this message]
2015-03-23 10:09 ` Andreas Leha
2015-03-23 8:56 ` Sebastien Vauban
2015-03-23 23:36 ` Nicolas Goaziou
2015-03-23 23:54 ` Andreas Leha
2015-03-24 7:13 ` Robert Klein
2015-03-24 8:41 ` Nicolas Goaziou
2015-03-24 9:04 ` Sebastien Vauban
2015-03-25 11:46 ` Robert Klein
2015-03-26 8:35 ` Sebastien Vauban
2015-03-26 13:06 ` Andreas Leha
2015-03-26 20:17 ` Nicolas Goaziou
2015-03-26 21:02 ` Andreas Leha
2015-03-27 11:02 ` Nicolas Goaziou
2015-03-27 11:24 ` Andreas Leha
2015-03-27 12:09 ` Robert Klein
2015-03-28 15:00 ` Nicolas Goaziou
2015-03-26 20:14 ` 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=874mpc6nii.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).