emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: comment section with latex_header
Date: Thu, 26 Mar 2015 21:02:40 +0000	[thread overview]
Message-ID: <olumw2zxyj3.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87lhijldia.fsf@nicolasgoaziou.fr

Hi Nicolas,

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>
>> FWIW, I agree that COMMENT should be equivalent to individual line # .
>
> I hope you mean it should be equivalent during export only. Otherwise,
> it would introduce some serious slowdown as COMMENT can be inherited.
>

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.

But I am not sure (hence my question below) whether there are use cases
that need different behaviour.

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

>> Sections that should be accessible without being exported get
>> the :noexport: tag.
>>
>> Is there any usecase for COMMENTed sections that is not covered
>> by :noexport:?
>
> Babel code from a :noexport: headline is executed. It isn't when in
> a COMMENT headline. I think both are useful.

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).

Regards,
Andreas

next prev parent reply	other threads:[~2015-03-26 21:02 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 [this message]
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=olumw2zxyj3.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

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).