emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: alain.cochard@unistra.fr
Cc: emacs-orgmode@gnu.org
Subject: [BUG] EXPORT_FILE_NAME keyword is used by `org-export-output-file-name' before macro expansion/INCLUDEs/removing COMMENTed trees (was: Confused about what the COMMENT keyword means)
Date: Sun, 02 Oct 2022 12:48:33 +0800	[thread overview]
Message-ID: <87k05i25lq.fsf@localhost> (raw)
In-Reply-To: <25398.44905.256243.690039@gargle.gargle.HOWL>

Alain.Cochard@unistra.fr writes:

> I can only hope that the "observed inconsistency" related to
> EXPORT_FILE_NAME can be resolved.

Well. I do consider this a bug. However, it is not easy to fix.
`org-export-output-file-name' is used across all ox-*.el backends,
including third-party packages, and it is called before we can determine
which parts of the exported file are going to be really exported.

I recommend you to use :EXPORT_FILE_NAME: headline property and export
using subtree scope.

> I still feel that section 13.6 of the manual can only been interpreted
> as: COMMENTing a tree is equivalent to commenting the tree.  I update
> my suggestion of addendum to the footnote:
>
>    Note that the subtree is still parsed and '#+KEYWORD: value' pairs
>    can contribute to calculation of buffer settings, in particular
>    '#+EXPORT_FILE_NAME: value'.
> Incidentally, could you provide another example of a buffer setting
> that would be taken into account even in a COMMENTed subtree?  (I
> tried a few without success.)

There should be no other buffer setting that is taken into account
in COMMENTed subtrees. EXPORT_FILE_NAME is the only one.

I think that we should not really change the manual unless we have to.
It will be better to fix the bug instead.

-- 
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92

Confirmed.


  reply	other threads:[~2022-10-02  4:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26 18:28 Confused about what the COMMENT keyword means Alain.Cochard
2022-09-27  1:55 ` Ihor Radchenko
2022-09-27  7:00   ` Alain.Cochard
2022-09-27  7:40     ` Ihor Radchenko
2022-09-30  8:57       ` Alain.Cochard
2022-10-02  4:48         ` Ihor Radchenko [this message]
2022-10-11 14:42           ` [BUG] EXPORT_FILE_NAME keyword is used by `org-export-output-file-name' before macro expansion/INCLUDEs/removing COMMENTed trees (was: Confused about what the COMMENT keyword means) Alain.Cochard
2022-10-18  8:53             ` Alain.Cochard
2022-11-10  1:56               ` Ihor Radchenko
2022-11-10  2:03             ` [FR] Allow TITLE to be used as default export file name (was: [BUG] EXPORT_FILE_NAME keyword is used by `org-export-output-file-name' before macro expansion/INCLUDEs/removing COMMENTed trees (was: Confused about what the COMMENT keyword means)) Ihor Radchenko
2022-11-10  7:53               ` Alain.Cochard
2022-11-10  8:04                 ` Ihor Radchenko
2022-11-10  1:51           ` [BUG] EXPORT_FILE_NAME keyword is used by `org-export-output-file-name' before macro expansion/INCLUDEs/removing COMMENTed trees (was: Confused about what the COMMENT keyword means) Ihor Radchenko

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=87k05i25lq.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=alain.cochard@unistra.fr \
    --cc=emacs-orgmode@gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).