From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Sebastien Vauban
<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: comment section with latex_header
Date: Thu, 26 Mar 2015 21:14:32 +0100 [thread overview]
Message-ID: <87pp7vldnb.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <86d23y3gxi.fsf@example.com> (Sebastien Vauban's message of "Tue, 24 Mar 2015 10:04:09 +0100")
Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
writes:
> Can't we say that a COMMENT'ed subtree is like having all of its
> contents commented, line by line? IOW, nothing "accessible"?
There is, at least, one problem. Comments are always comments (really).
However COMMENT keyword is only active during export. That means the
behaviour will differ unexpectedly when exporting a document, as
reported by Robert Klein.
Anyway, anything is possible as long as it is clearly documented.
Regards,
prev parent reply other threads:[~2015-03-26 20:14 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
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 [this message]
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=87pp7vldnb.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.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).