alain.coch...@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.
