From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 48404@debbugs.gnu.org, stefan@marxist.se, tsdh@gnu.org
Subject: bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command
Date: Sun, 16 May 2021 17:27:19 +0300 [thread overview]
Message-ID: <835yzivjnc.fsf@gnu.org> (raw)
In-Reply-To: <87cztqojsk.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 16 May 2021 16:06:03 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: tsdh@gnu.org, 48404@debbugs.gnu.org, stefan@marxist.se
> Date: Sun, 16 May 2021 16:06:03 +0200
>
> > But this comes with a heavy price: commands from any package that is
> > not bundled with Emacs will not be able to take advantage of this
> > feature, ever. Is it worth punishing those packages' users to have a
> > softer transition? Given our conservative approach to obsoleting
> > stuff, I'm not sure.
>
> I'm not quite sure I understand you here? If the version can't be
> parsed, then the command will still show up in `M-x TAB', which means
> that the obsoletion of these commands is very soft indeed.
For obsolete commands from 3rd-party packages, which state something
like "Magit 3.0" in the version since which they are obsolete, the
obsolescence will never happen, in the sense that they will _always_
appear in "M-x TAB", even 100 years from now. Is that what we want?
> But I'm wondering whether `version-to-list' should be more lax here.
> That is, currently it'll barf of things like:
>
> (version-to-list "28.1 Magit/2.5")
I'm not sure it's possible without introducing ambiguity into the
version string and complicating comparison of versions. We already
support some non-numeric versions, and that's not easy.
> It might make sense to allow the obsoletion versions to refer to both an
> (approximate) Emacs version, as well as a package version.
How can this be done, even in principle? Versions of unbundled
packages are unrelated to Emacs versions; typically, a given version
of an unbundled package supports quite a few Emacs versions. So what
Emacs version will you put there?
next prev parent reply other threads:[~2021-05-16 14:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 20:45 bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command Tassilo Horn
2021-05-14 6:21 ` Eli Zaretskii
2021-05-14 6:47 ` Tassilo Horn
2021-05-14 7:18 ` Eli Zaretskii
2021-05-14 7:28 ` Eli Zaretskii
2021-05-14 7:43 ` Lars Ingebrigtsen
2021-05-14 7:56 ` Eli Zaretskii
2021-05-16 14:06 ` Lars Ingebrigtsen
2021-05-16 14:27 ` Eli Zaretskii [this message]
2021-05-16 14:38 ` Lars Ingebrigtsen
2021-05-16 14:48 ` Eli Zaretskii
2021-05-17 13:54 ` Lars Ingebrigtsen
2021-05-17 14:10 ` Eli Zaretskii
2021-05-17 14:20 ` Lars Ingebrigtsen
2021-05-17 14:27 ` Eli Zaretskii
2021-05-18 13:31 ` Lars Ingebrigtsen
2021-05-19 11:54 ` Tassilo Horn
2021-05-19 13:59 ` Eli Zaretskii
2021-05-14 7:41 ` Lars Ingebrigtsen
2021-05-14 16:45 ` Stefan Kangas
2021-05-14 16:51 ` Lars Ingebrigtsen
2021-05-14 7:50 ` bug#48404: Daniel Mendler
2021-05-14 18:31 ` bug#48404: Daniel Mendler
2021-05-16 14:09 ` bug#48404: Lars Ingebrigtsen
2021-05-16 20:26 ` bug#48404: Daniel Mendler
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=835yzivjnc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48404@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
--cc=tsdh@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.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).