emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bastien.guerry@wikimedia.fr>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [CONCERN] Orgmode version string
Date: Thu, 28 Oct 2010 16:06:56 +0200	[thread overview]
Message-ID: <8762wm5s3j.fsf@gnu.org> (raw)
In-Reply-To: <8162wmze0s.fsf@gmail.com> (Jambunathan K.'s message of "Thu, 28 Oct 2010 18:10:35 +0530")

Jambunathan K <kjambunathan@gmail.com> writes:

> I have every reason to believe that upcoming version of Org would be
> tagged as 7.02. Earlier I had argued that version strings be
> version-to-list compatible. I would like to reiterate it.
>
> My real concern is that 7.02 would be deemed as equivalent to 7.2
> internally by the versioning subsystem and this is likely to clash with
> user's point of view. A user would *definitely* assume 7.02 as different
> from 7.2 and in all probability swear that former is inferior to the
> later.
>
> Please confirm what I am saying by evalling this:
>
> #+begin_src emacs-lisp
>   (version-list-= (version-to-list "7.02") (version-to-list "7.2"))
> #+end_src

I confirm.

> Ignore this mail if it is already taken care of. Needless to say, I have
> ELPA-tarballs in mind when I say this.

Another way is to make Emacs more liberal about version names.

Can you suggest a new default for `version-regexp-alist' so that
7.01 is considered older than 7.10?

(version-list-= (version-to-list "7.02") (version-to-list "7.2"))
being t is not intuitive.

-- 
 Bastien

  reply	other threads:[~2010-10-28 14:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28 12:40 [CONCERN] Orgmode version string Jambunathan K
2010-10-28 14:06 ` Bastien [this message]
2010-10-28 16:27   ` Jambunathan K
2010-10-28 18:16   ` Jambunathan K
2010-10-28 21:57 ` Carsten Dominik
2010-10-29  1:36   ` Jambunathan K
2010-10-29 13:06   ` Jambunathan K
2010-10-29 14:51     ` Carsten Dominik
2010-10-29 17:53       ` Jambunathan K
2010-10-29 14:53     ` Bastien

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=8762wm5s3j.fsf@gnu.org \
    --to=bastien.guerry@wikimedia.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@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).