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: Tue, 27 Sep 2022 09:00:51 +0200	[thread overview]
Message-ID: <25394.40867.872373.589874@gargle.gargle.HOWL> (raw)
In-Reply-To: <87leq5pomk.fsf@localhost>


Thanks for answering.

Ihor Radchenko writes on Tue 27 Sep 2022 09:55:
 > Alain.Cochard@unistra.fr writes:
 > 
 > > Hello.  I have the file:
 > >
 > >    * COMMENT foo
 > >    #+EXPORT_FILE_NAME: foo.pdf
 > >    #+TITLE: foot
 > >    fofoo
 > >    * bar
 > >    #+EXPORT_FILE_NAME: bar.pdf
 > >    #+TITLE: bart
 > >    babar
 > 
 > #+EXPORT_FILE_NAME is an in-buffer export setting with global effect.
 > According to 13.2 Export Settings section of the Org manual,
 > 
 >        In-buffer settings may appear anywhere in the file, either directly
 >     or indirectly through a file included using ‘#+SETUPFILE: filename or
 >     URL’ syntax.
 > 
 > Because export settings are global, they have higher priority over the
 > COMMENTed heading.

OK, I can understand that but if, as I now see in 13.2, both TITLE and
EXPORT_FILE_NAME are export settings, why does it behaves as I expect
for TITLE (the title I get is indeed 'bart') but not for
EXPORT_FILE_NAME?

 > [...]
 
 > > By contrast, with this file
 > > 
 > >    # * foo
 > >    # #+EXPORT_FILE_NAME: foo.pdf
 > >    # #+TITLE: foot
 > >    # fofoo
 > >    * bar
 > >    #+EXPORT_FILE_NAME: bar.pdf
 > >    #+TITLE: bart
 > >    babar
 > 
 > This file contains no export settings.

I don't understand that: what about the line '#+EXPORT_FILE_NAME:
bar.pdf'??

 > # #+EXPORT_FILE_NAME: foo.pdf line is not an export setting. It
 > does not matter that it is a comment,

Yes, of course; if it is a comment, it is as if it were not here at
all, correct?

 > I think that the manual is not clear enough about applying
 > in-buffer settings and keywords. We may want to clarify this
 > detail.

How about adding a sentence in 13.6, perhaps in the footnote?
Something like "Also note that, as mentioned in 13.2, export
settings, being global, take precedence over the 'COMMENT' keyword."

Finally, I'd appreciate a "SUPERCOMMENT" keyword, which would be
equivalent (when exporting) to removing the tree altogether (or, as I
understand, prepending '# ' to each line of the tree).




-- 
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-27  7:53 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 [this message]
2022-09-27  7:40     ` Ihor Radchenko
2022-09-30  8:57       ` Alain.Cochard
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=25394.40867.872373.589874@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).