From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Leha Subject: Re: [Bug] New LaTeX exporter ignoring noexport Date: Sun, 06 May 2012 22:39:09 +0200 Message-ID: <87bom111ua.fsf@med.uni-goettingen.de> References: <87ipg913ie.fsf@med.uni-goettingen.de> <87aa1lgiqk.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:41966) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SR8FP-00056x-Er for emacs-orgmode@gnu.org; Sun, 06 May 2012 16:40:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SR8FN-0004RS-MM for emacs-orgmode@gnu.org; Sun, 06 May 2012 16:40:03 -0400 Received: from plane.gmane.org ([80.91.229.3]:39645) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SR8FN-0004RB-Ew for emacs-orgmode@gnu.org; Sun, 06 May 2012 16:40:01 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SR8FJ-0003xD-W6 for emacs-orgmode@gnu.org; Sun, 06 May 2012 22:39:57 +0200 Received: from vpn-2061.gwdg.de ([134.76.2.61]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 May 2012 22:39:57 +0200 Received: from andreas.leha by vpn-2061.gwdg.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 06 May 2012 22:39:57 +0200 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 Nicolas, Nicolas Goaziou writes: > Hello, > > Andreas Leha writes: > >> for me the new latex exporter seems to ignore the :noexport: tag with >> regard to source block execution. >> >> If I export this example, both source blocks get evaluated. > > :noexport: isn't a directive that Babel recognizes. As a consequence, > a :noexport: tag won't prevent a source block from being executed. > There are other ways to specify it at the Babel level, though. > > On the other hand, a :noexport: tag prevents a subtree from being > published, which is what happens here, as far as I can tell. > > Therefore, I don't qualify this as a bug. Fair enough. I was just surprised, that the new exporter behaves differently from the old one in this respect. ( And I still think, that 1) the differentiation between babel and export wrt :noexport: is not intuitive and 2) turning off evaluation for a subtree on "Babel level", is not as straight forward and visual as the simple :noexport: tag. So all in all I'll miss this feature in the new exporter. ) Regards, Andreas