unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.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: Mon, 17 May 2021 15:54:43 +0200	[thread overview]
Message-ID: <87h7j1lb30.fsf@gnus.org> (raw)
In-Reply-To: <834kf2viof.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 16 May 2021 17:48:16 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> >> (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.
>> 
>> Sorry, I was imprecise here -- I didn't mean that we should change
>> `version-to-list' itself here, but add a new function that's more
>> permissive, just for use in this context.  It would basically be
>> something along the lines of (version-to-list (car (split-string string))) 
>
> The main purpose is to compare versions.  How would you do that with
> loose version strings such as the one above?

We're looking at the Emacs version (which we'd put first in the version
string, while the rest is essentially a free text used as a comment).

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-05-17 13:54 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
2021-05-16 14:38               ` Lars Ingebrigtsen
2021-05-16 14:48                 ` Eli Zaretskii
2021-05-17 13:54                   ` Lars Ingebrigtsen [this message]
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=87h7j1lb30.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=48404@debbugs.gnu.org \
    --cc=eliz@gnu.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).