emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alain.Cochard@unistra.fr
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Alain.Cochard@unistra.fr, emacs-orgmode@gnu.org
Subject: Re: Confused about what the COMMENT keyword means
Date: Fri, 30 Sep 2022 10:57:13 +0200	[thread overview]
Message-ID: <25398.44905.256243.690039@gargle.gargle.HOWL> (raw)
In-Reply-To: <87o7v1nu2e.fsf@localhost>

Ihor Radchenko writes on Tue 27 Sep 2022 15:40:

 > However `org-export-as' is generally called inside
 > `org-export-to-file' and `org-export-to-file' needs to know which
 > file to export to in advance; before the buffer is stripped of
 > commented trees. That's why there is the observed inconsistency
 > between EXPORT_FILE_NAME and TITLE settings.

 > [...]
 
 > If you have something like
 > 
 > * COMMENT heading
 > #+KEYWORD: value
 > 
 > Org does look inside:
 > (heading (:commentedp t) (keyword))
 > 
 > Then, such keyword can contribute to calculation of buffer
 > settings.  It is only `org-export-as' that makes special
 > arrangement and physically removes COMMENTed subtrees before
 > exporting the buffer.
 > 
 > Hope it is now more clear.

Yes, thanks a lot, much clearer.

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

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.)

Regards

-- 
EOST (École et Observatoire des Sciences de la Terre) 
ITE (Institut Terre & Environnement) | alain.cochard@unistra.fr
5 rue René Descartes   [bureau 106]  | Phone: +33 (0)3 68 85 50 44 
F-67084 Strasbourg Cedex, France     | [ slot available for rent ]



  reply	other threads:[~2022-09-30  8:59 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 [this message]
2022-10-02  4:48         ` [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-10-11 14:42           ` 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=25398.44905.256243.690039@gargle.gargle.HOWL \
    --to=alain.cochard@unistra.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    /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).