From: Jim Porter <jporterbugs@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Rename headline to heading
Date: Sun, 15 Aug 2021 15:32:22 -0700 [thread overview]
Message-ID: <sfc4lm$ggf$1@ciao.gmane.io> (raw)
In-Reply-To: <87v947wr7s.fsf@gmail.com>
On 8/14/2021 3:54 PM, Tim Cross wrote:
> I'm not convinced a transition period will help in this case. At some
> point, users will need to update their capture templates regardless.
> Provided this impact is clearly outlined in the NEWS.org file (I think
> there should be a specific reference to capture templates added in the
> patch to NEWS.org) and provided this change is applied to the next
> release only, no transition period is necessary.
I think having a transition period would be helpful here. First, this
helps to account for users who may run multiple versions of Emacs with
the same config. This could happen for a few reasons, such as running on
different revisions of a GNU/Linux distribution, or even just because
the user is testing out the latest/next version of Emacs.
In addition, a transition period makes it easy to inform users about
what they need to do to upgrade. Without any compatibility code, the
error message (likely) won't be very helpful, whereas even some minimal
compatibility code could tell the user what edits to make to their
config. While everyone *should* read the manual/NEWS, it's easy to miss
things sometimes, and errors like this can be non-obvious, especially if
the compatibility issue isn't directly in the user's config, but in some
other third-party package.
As such, I think it would be nice to have a transition period of at
least one Emacs version. Beyond that, I don't see any problems with
excising old compatibility code. As you say, users will have to upgrade
at *some* point.
- Jim
next prev parent reply other threads:[~2021-08-15 22:33 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 [this message]
2021-08-15 23:17 ` Tim Cross
2021-08-16 0:38 ` Jim Porter
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='sfc4lm$ggf$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).