From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: comment section with latex_header Date: Fri, 27 Mar 2015 12:02:38 +0100 Message-ID: <87iodmk8j5.fsf@nicolasgoaziou.fr> References: <87d23znv5a.fsf@nicolasgoaziou.fr> <55110E84.3060408@roklein.de> <87zj72n5xk.fsf@nicolasgoaziou.fr> <86d23y3gxi.fsf@example.com> <5512A024.5050509@roklein.de> <86k2y4b1gt.fsf@example.com> <87lhijldia.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47173) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YbS12-0000zO-Pp for emacs-orgmode@gnu.org; Fri, 27 Mar 2015 07:01:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YbS0x-0000n5-Rt for emacs-orgmode@gnu.org; Fri, 27 Mar 2015 07:01:28 -0400 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:43485) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YbS0x-0000m6-Mp for emacs-orgmode@gnu.org; Fri, 27 Mar 2015 07:01:23 -0400 In-Reply-To: (Andreas Leha's message of "Thu, 26 Mar 2015 21:02:40 +0000") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Andreas Leha Cc: emacs-orgmode@gnu.org Andreas Leha 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 =E2=80=98COMMENT=E2=80=99 keyword at the beginning of an en= try, 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,