From: Bastien <bzg@gnu.org>
To: Timothy <tecosaur@gmail.com>
Cc: Matt Huszagh <huszaghmatt@gmail.com>,
emacs-orgmode@gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Supported Emacs version
Date: Mon, 22 Nov 2021 07:39:22 +0100 [thread overview]
Message-ID: <87fsrolmn9.fsf@gnu.org> (raw)
In-Reply-To: <87a6hw7lxb.fsf@gmail.com> (Timothy's message of "Mon, 22 Nov 2021 14:12:44 +0800")
Hi Timothy,
Timothy <tecosaur@gmail.com> writes:
> Personally I’m more inclined towards an all-or-nothing approach.
I understand this inclination but I disagree.
Org is made of many areas and partial backward-compatibility can
still be useful. When people report compatibility problems with
Emacs <26, we can guide them so that they enhance org-compat.el.
It is not because we don't promise compatibility for Emacs < 26
that we should prevent backward-compatibility for Emacs < 26, and
the all-or-nothing approach would actually prevent it.
I hope this is convincing enough :)
--
Bastien
next prev parent reply other threads:[~2021-11-22 6:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 18:41 [PATCH] Fix window width when line numbers present Matt Huszagh
2021-11-21 19:14 ` Timothy
2021-11-21 21:08 ` Nicolas Goaziou
2021-11-21 21:14 ` Matt Huszagh
2021-11-21 21:16 ` Bastien
2021-11-21 21:22 ` Matt Huszagh
2021-11-22 5:14 ` Bastien
2021-11-22 5:31 ` Timothy
2021-11-22 5:44 ` Bastien
2021-11-22 5:51 ` Supported Emacs version (was: [PATCH] Fix window width when line numbers present) Timothy
2021-11-22 6:05 ` Supported Emacs version Bastien
2021-11-22 6:12 ` Timothy
2021-11-22 6:39 ` Bastien [this message]
2021-11-22 8:04 ` Timothy
2021-11-22 10:26 ` Bastien
2021-11-22 11:55 ` [PATCH] Fix window width when line numbers present Ihor Radchenko
2021-11-22 12:40 ` Tim Cross
2021-11-23 5:59 ` Bastien
2021-11-23 7:05 ` Tim Cross
2021-11-22 3:16 ` Timothy
2021-11-21 19:19 ` Timothy
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=87fsrolmn9.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=huszaghmatt@gmail.com \
--cc=mail@nicolasgoaziou.fr \
--cc=tecosaur@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).