all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: RE: next emacs version?
Date: Fri, 19 Mar 2010 10:29:40 -0700	[thread overview]
Message-ID: <E96EDFC4C6CA4CEAACDA129439B4A625@us.oracle.com> (raw)
In-Reply-To: <83iq8sigyq.fsf@gnu.org>

> > What will the next Emacs version be?
> 
> 23.2

Confirms what I thought.

> > 24.0.50.1
> > But I thought the next release would be Emacs 23.2, not 24.
> 
> That's not a contradiction.  Emacs 23.2 will be delivered from a
> branch, not from the trunk.  Version 24.0.50 is from the development
> trunk.

Also confirms what I thought. Thanks.

> > What is the proper test (or a reasonable test) to use in the
> > code, for this change? It's OK if I don't support the change
> > until the release is out. It's the test for the
> > official release I'm most interested in. (But I'm also 
> > interested in advice about testing against an in-development version.)
> 
> If you want to discern v23.x from v24.x, emacs-major-version is the
> first thing I'd try.

I said I want to discern this code change, which will be made by Emacs Dev to
23.2 (probably; it is made now in 24.0.50.1). So `emacs-major-version' is not
the way to check that.

In the past, I've checked `emacs-major-version' and `emacs-minor-version'
together, or I've checked for the change using string-match with
`emacs-version'. I was wondering if there is a recommendation here.

And I was wondering if there isn't a simple check that will match anything more
recent than the release 23.1. That is, including the dev version 24.0.50.1 and
the next release, 23.2. That's a typical use case for me: Emacs Dev has changed
something after the last release and I expect that the change will remain in
place for the new release. 

Yes, obviously, if the change is in fact removed before the new release then my
test will no longer be accurate. But that's the minority of such cases, in my
experience, and I can live with that maintenance problem.

Obviously, if there is a more pertinent test such as a new variable or function,
I use that instead. But this example is pretty typical of the problem. The value
of a regexp variable has changed, and that changes the behavior of the code. I
need to test which regexp value is in use, the old one or the new one.

FWIW, the regexp in question, `directory-listing-before-filename-regexp', is
among the hairiest I've come across (have a look - quite amusing), and I don't
think it's a good idea to try to test against that value. I see no alternative
but to test the Emacs version. (This affects Dired font-locking. The new value
of the regexp adds a level of group nesting.)





  reply	other threads:[~2010-03-19 17:29 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 11:23 next emacs version? Drew Adams
2010-03-19 13:22 ` Eli Zaretskii
2010-03-19 17:29   ` Drew Adams [this message]
2010-03-19 18:09     ` Eli Zaretskii
2010-03-19 18:46       ` Drew Adams
2010-03-19 19:02         ` Eli Zaretskii
2010-03-19 20:02           ` Drew Adams
2010-03-19 21:15             ` Eli Zaretskii
2010-03-19 21:23               ` Drew Adams
2010-03-20  2:35                 ` Ken Raeburn
2010-03-20  2:39                   ` Lennart Borgman
2010-03-20  3:42                     ` Óscar Fuentes
2010-03-20 15:51                       ` Lennart Borgman
2010-03-20  5:31                     ` Ken Raeburn
2010-03-23  2:05                     ` Stephen J. Turnbull
2010-03-20  3:38                   ` Drew Adams
2010-03-20  5:31                     ` Ken Raeburn
2010-03-20  6:51                       ` Drew Adams
2010-03-20  5:31                     ` Ken Raeburn
2010-03-20  6:51                       ` Drew Adams
2010-03-23  2:34                     ` Stephen J. Turnbull
2010-03-23  5:01                       ` Miles Bader
2010-03-23  5:39                       ` Drew Adams
2010-03-20  3:51                 ` Jason Rumney
2010-03-20  6:47                   ` Drew Adams
2010-03-20  8:39                   ` Eli Zaretskii
2010-03-20 14:58                     ` Drew Adams
2010-03-20 16:22                       ` Eli Zaretskii
2010-03-20  8:11                 ` Eli Zaretskii
2010-03-19 20:55           ` Stefan Monnier
2010-03-19 21:16             ` Drew Adams
2010-03-20 19:10               ` Stefan Monnier
2010-03-20 20:29                 ` Drew Adams
2010-03-20 21:53                   ` Stefan Monnier
2010-03-20 23:09                     ` Drew Adams
2010-03-20 23:26                       ` Drew Adams
2010-03-22  1:22                       ` Stefan Monnier
2010-03-22  7:22                         ` Drew Adams
2010-03-22 13:52                           ` Stefan Monnier
2010-03-21 21:34     ` Thien-Thi Nguyen
2010-03-21 23:20       ` Drew Adams
2010-03-19 14:52 ` Chong Yidong

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E96EDFC4C6CA4CEAACDA129439B4A625@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.