To: Ihor Radchenko <email@example.com>
Cc: Alain.Cochard@unistra.fr, Ihor Radchenko <firstname.lastname@example.org>,
Subject: Re: [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))
Date: Thu, 10 Nov 2022 08:53:06 +0100 [thread overview]
Message-ID: <email@example.com.HOWL> (raw)
Ihor Radchenko writes on Thu 10 Nov 2022 02:03:
> Alain.Cochard@unistra.fr writes:
> > > I recommend you to use :EXPORT_FILE_NAME: headline property and
> > > export using subtree scope.
> > Thanks a lot for the tip. A suggestion: that the :TITLE:
> > property be used if it exists.
> We currently fall back to file name if nothing else works. Using
> TITLE is possible but cannot be done by default as a fallback ---
> existing users relying on current behaviour will be affected by
> such change.
> We may add a defcustom though. It will be nil by default and
> setting it to non-nil will make Org export fall back to TITLE
> rather than file name.
> However, there is no point adding yet another option if not many
> users are interested. I am changing the subject of this email to
> facilitate the feedback.
I am surprised by this message: like I said earlier when replying to
myself to the same message as the one to which you are replying, I
discovered the :EXPORT_TITLE: (headline) property, which does exactly
what I was looking for.
It is as if you missed that message of mine (or did not understand
what I wanted to say) AND forgot or don't know about the
:EXPORT_TITLE: property. As I find it rather unlikely, I guess you
are thinking of something else, which is beyond me.
At any rate, there is no need for anything new in this repect, even
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) | firstname.lastname@example.org
5 rue René Descartes [bureau 110] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | [ slot available for rent ]
next prev parent reply other threads:[~2022-11-10 7:54 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 ` [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 [this message]
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
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).