all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
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: Sat, 22 Apr 2017 09:34:20 +0200	[thread overview]
Message-ID: <87k26cvqtf.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <877f2d9aqf.fsf@gmx.us> (rasmus@gmx.us's message of "Fri, 21 Apr 2017 15:00:24 +0200")

Hello,

Rasmus <rasmus@gmx.us> writes:

> Stefan Kredler <eska1969@gmail.com> 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?

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2017-04-22  7:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21  8:16 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/) Stefan Kredler
2017-04-21 13:00 ` Rasmus
2017-04-22  7:34   ` Nicolas Goaziou [this message]
2017-04-23 17:32     ` Rasmus
2017-04-23 17:50       ` Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k26cvqtf.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.