emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: comment section with latex_header
Date: Fri, 27 Mar 2015 12:02:38 +0100	[thread overview]
Message-ID: <87iodmk8j5.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <olumw2zxyj3.fsf@med.uni-goettingen.de> (Andreas Leha's message of "Thu, 26 Mar 2015 21:02:40 +0000")

Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:

> I see.  I did not consider any possible slow-downs.  I'd expect COMMENT
> to behave exactly like # in every regard -- not only export.  That is a
> clearly defined behaviour, that should not produce confusion.

As explained, this is not realistic.

> If COMMENT is only valid for export, then I would actually recommend
> to rename it to make that clear.

The manual is, IMO,  pretty explicit:

     Finally, a ‘COMMENT’ keyword at the beginning of an entry, but after
  any other keyword or priority cookie, comments out the entire subtree.
  In this case, the subtree is not exported and no code block within it is
  executed either.  The command below helps changing the comment status of
  a headline.

> I completely agree.  My question was, what a use case would be that
> requires a COMMENT that behaves different from #'ing the individual
> lines (and is not covered by :noexport: already).

I don't think there is any. This is basically what my first patch did
(i.e., removing any COMMENT subtree at the very beginning of export
process), but it nevertheless surprised some users.

Regards,

  reply	other threads:[~2015-03-27 11: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
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 [this message]
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=87iodmk8j5.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=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).