From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Leha Subject: Re: comment section with latex_header Date: Thu, 26 Mar 2015 13:06:05 +0000 Message-ID: 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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34416) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yb7US-0000Jx-LH for emacs-orgmode@gnu.org; Thu, 26 Mar 2015 09:06:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yb7UN-0001KD-N6 for emacs-orgmode@gnu.org; Thu, 26 Mar 2015 09:06:28 -0400 Received: from plane.gmane.org ([80.91.229.3]:55115) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yb7UN-0001Jy-Gl for emacs-orgmode@gnu.org; Thu, 26 Mar 2015 09:06:23 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Yb7U8-00010t-BR for emacs-orgmode@gnu.org; Thu, 26 Mar 2015 14:06:08 +0100 Received: from 193.63.223.66 ([193.63.223.66]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 26 Mar 2015 14:06:08 +0100 Received: from andreas.leha by 193.63.223.66 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 26 Mar 2015 14:06:08 +0100 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 all, Sebastien Vauban writes: > Robert Klein wrote: >> On 03/24/2015 10:04 AM, Sebastien Vauban wrote: >> >>> Can't we say that a COMMENT'ed subtree is like having all of its >>> contents commented, line by line? IOW, nothing "accessible"? >> >> This would probably break a lot of babel stuff. > > Could you elaborate why? > >> If there was an option to disable exports for #+NAME:-ed stuff (i.e. >> data sources for babel), e.g. somtehing like >> >> #+NAME: xyzzy :exports none >> | munich | 13 | >> | cologne | 12 | >> >> you could deprecate and eventually disable data sources in COMMENT-ed >> section. > > If you *not to export* some stuff in a subtree, adding the "noexport" > tag would be enough, right? > > Best regards, > Seb FWIW, I agree that COMMENT should be equivalent to individual line # . 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:? Regards, Andreas