Re: [O] 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/)

[Rasmus]

Nicolas Goaziou <address@hidden> 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!