[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-c
From: |
Lars Ingebrigtsen |
Subject: |
bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command |
Date: |
Sun, 16 May 2021 16:06:03 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
>> The idea is to have a softer transition when obsoleting commands -- `M-x
>> some-obsoleteTAB' will list the command if it's been "recently"
>> obsoleted, but also list the new command name (in parentheses). This
>> will hopefully help people to learn the new command name.
>
> 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.
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")
It might make sense to allow the obsoletion versions to refer to both an
(approximate) Emacs version, as well as a package version.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Tassilo Horn, 2021/05/13
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Eli Zaretskii, 2021/05/14
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Tassilo Horn, 2021/05/14
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Eli Zaretskii, 2021/05/14
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Eli Zaretskii, 2021/05/14
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Lars Ingebrigtsen, 2021/05/14
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Eli Zaretskii, 2021/05/14
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command,
Lars Ingebrigtsen <=
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Eli Zaretskii, 2021/05/16
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Lars Ingebrigtsen, 2021/05/16
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Eli Zaretskii, 2021/05/16
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Lars Ingebrigtsen, 2021/05/17
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Eli Zaretskii, 2021/05/17
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Lars Ingebrigtsen, 2021/05/17
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Eli Zaretskii, 2021/05/17
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Lars Ingebrigtsen, 2021/05/18
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Tassilo Horn, 2021/05/19
- bug#48404: 28.0.50; "Invalid version syntax" errors with read-extended-command, Eli Zaretskii, 2021/05/19