From: Jim Porter <jporterbugs@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Rename headline to heading
Date: Sun, 15 Aug 2021 17:38:04 -0700 [thread overview]
Message-ID: <sfcc1c$6qd$1@ciao.gmane.io> (raw)
In-Reply-To: <877dgmi89p.fsf@gmail.com>
On 8/15/2021 4:17 PM, Tim Cross wrote:
> At some point, your transition period will end. If it isn't with the
> transition to v9.5, it will be the transition to 9.6. At this point, all
> of the issues you point out will still exist. There will still be people
> who are running multiple versions, there will still be people who failed
> to read or comprehend the impact of the change. All that the transition
> does is delay the pain point while adding additional complexity to the
> code base. Admittedly, in this case, the additional complexity is very
> small.
I think it does more than *just* delaying the pain. It's true that the
transition period will end, and any users who haven't updated their
configs by then will have a broken config. However, some percentage of
users will upgrade Org, see the warning, fix their configs (perhaps not
immediately, but in the next few weeks), and continue on with minimal
pain. Of course, I'm sure most users would make the necessary change
even without a transition period, but the transition period gives users
a bit more flexibility in determining when to update their configs.
In any case, if Org were to add an informative message about this
change, `org-capture-upgrade-templates' seems to me a reasonable place
to do it since it's already doing this for other obsolete types. In
fact, looking at the commit history, that function was added in Feb 2017
(in commit 0f1b5ec496), so perhaps it's been long enough that the old
datetree migration could be removed entirely and be replaced with this
new headline -> heading migration. That would have the net effect of
*reducing* the total amount of compatibility code.
That said, this isn't a critical issue for me either way. I keep Emacs
and Org pretty up to date so I shouldn't have a problem when the time
comes to make this change in my config.
- Jim
next prev parent reply other threads:[~2021-08-16 0:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 12:12 [PATCH] Rename headline to heading André A. Gomes
2021-08-05 15:04 ` Maxim Nikulin
2021-08-14 22:54 ` Tim Cross
2021-08-15 16:22 ` No Wayman
2021-08-15 16:50 ` No Wayman
2021-08-15 22:32 ` Jim Porter
2021-08-15 23:17 ` Tim Cross
2021-08-16 0:38 ` Jim Porter [this message]
2021-08-16 1:18 ` Tim Cross
2021-08-08 16:59 ` Tom Gillespie
2021-08-14 23:19 ` Tim Cross
2021-09-19 11:06 ` Timothy
2021-09-30 12:08 ` André A. Gomes
2021-09-26 9:27 ` Bastien
2021-09-30 12:21 ` André A. Gomes
2021-10-01 8:38 ` Bastien
2021-10-15 8:52 ` André A. Gomes
2021-10-15 9:56 ` Timothy
2021-10-15 10:18 ` André A. Gomes
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='sfcc1c$6qd$1@ciao.gmane.io' \
--to=jporterbugs@gmail.com \
--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).