From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: Bug: export does not ignore #+INCLUDE if archived or tagged :noexport: Package: Org mode version 9.0.5 (9.0.5-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20170210/) Date: Sun, 23 Apr 2017 19:32:58 +0200 Message-ID: <877f2bf2r9.fsf@gmx.us> References: <4eea3f8a-cda4-4b10-996f-41e10a723fb2@Spark> <877f2d9aqf.fsf@gmx.us> <87k26cvqtf.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36856) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d2LNi-000555-3b for emacs-orgmode@gnu.org; Sun, 23 Apr 2017 13:33:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d2LNf-000835-1w for emacs-orgmode@gnu.org; Sun, 23 Apr 2017 13:33:06 -0400 Received: from mout.gmx.net ([212.227.15.15]:63869) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d2LNe-00082e-OC for emacs-orgmode@gnu.org; Sun, 23 Apr 2017 13:33:02 -0400 In-Reply-To: <87k26cvqtf.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sat, 22 Apr 2017 09:34:20 +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" To: mail@nicolasgoaziou.fr Cc: emacs-orgmode@gnu.org Nicolas Goaziou writes: >>> when archiving sections or exclude them from export I would expect >>> them being exempt from being evaluated during export. >>> The section archived or marked as ~:no export:~ is still evaluated >>> and there is an error >>> if the reference in the include file is no longer available. I get >>> the error message >>> ~"org-export-expand-include-keyword: Cannot include file ~/filename.org"~ >> >> IMO this is a feature. I have used this before, for instance when >> including tables used in source blocks at export time. > > I agree an included file could introduce Babel contents which would then > be processed, even though the tree is not exported. > > However, COMMENT keyword prevents Babel evaluation, so we could avoid > expanding include keywords in this particular case. > > WDYT? It's fine to exclude #+include in COMMENT headlines IMO. Cheers, Rasmus -- Spil noget med Slayer!