From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Klein Subject: Re: comment section with latex_header Date: Fri, 27 Mar 2015 13:09:35 +0100 Message-ID: <5515487F.1020208@roklein.de> 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> <87iodmk8j5.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33733) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YbT56-0002vK-Qf for emacs-orgmode@gnu.org; Fri, 27 Mar 2015 08:09:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YbT51-0002Rt-Sa for emacs-orgmode@gnu.org; Fri, 27 Mar 2015 08:09:44 -0400 Received: from gate1.mpip-mainz.mpg.de ([194.95.63.248]:57628) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YbT51-0002QT-LX for emacs-orgmode@gnu.org; Fri, 27 Mar 2015 08:09:39 -0400 Received: from [10.20.2.71] (port=39273 helo=vmmail1.mpip-mainz.mpg.de) by gate1.mpip-mainz.mpg.de with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1YbT4x-0003G5-0t for emacs-orgmode@gnu.org; Fri, 27 Mar 2015 13:09:35 +0100 Received: from pckr150.mpip-mainz.mpg.de ([10.20.70.90]) by vmmail1.mpip-mainz.mpg.de with esmtp (Exim 4.72) (envelope-from ) id 1YbT4x-0004e8-52 for emacs-orgmode@gnu.org; Fri, 27 Mar 2015 13:09:35 +0100 In-Reply-To: <87iodmk8j5.fsf@nicolasgoaziou.fr> 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: emacs-orgmode@gnu.org Hi, On 03/27/2015 12:02 PM, Nicolas Goaziou wrote: > Andreas Leha writes: >> 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. > Just a note: I didn't know of :noexport: before Andreas brought it up in this thread. If you revert the second patch, please put a note in the release notes for the next org release, so the other babel users know a migration path. Best regards Robert