From: Dan Nicolaescu <dann@ics.uci.edu>
To: rms@gnu.org
Cc: juri@jurta.org, Andreas Schwab <schwab@suse.de>, emacs-devel@gnu.org
Subject: Re: accept more version names in file-name-sans-versions
Date: Sat, 22 Sep 2007 09:20:40 -0700 [thread overview]
Message-ID: <200709221620.l8MGKeR4006966@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <E1IZ7DR-0001GS-Dw@fencepost.gnu.org> (Richard Stallman's message of "Sat\, 22 Sep 2007 11\:48\:21 -0400")
Richard Stallman <rms@gnu.org> writes:
> Now if you are checking out revision EMACS_22_BASE it still does not
> work. :-)
>
> Could you please send me a *precise* test case for this bug? The test
> case should start with `emacs -q', so that your .emacs file does not
> affect it, and it should show exactly what text to put in the buffer,
> what commands to execute, and how and where to click. Also please say
> exactly what incorrect results you get.
The problem is fixed now on the EMACS_22_BASE branch, it will
propagate to the trunk whenever Miles restarts his merging.
There was a precise description in the original message, it was using
git. Here's one using CVS:
emacs -q
C-x C-f emacs/lisp/subr.el RET
C-u C-x v ~ EMACS_22_BASE RET
Before the fix the resulting buffer subr.el.~EMACS_22_BASE~ was not
put in emacs-lisp-mode, but in fundamental-mode.
next prev parent reply other threads:[~2007-09-22 16:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 1:14 accept more version names in file-name-sans-versions Dan Nicolaescu
2007-09-20 8:52 ` Juri Linkov
2007-09-22 2:14 ` Dan Nicolaescu
2007-09-22 8:52 ` Andreas Schwab
2007-09-22 15:48 ` Richard Stallman
2007-09-22 16:00 ` Andreas Schwab
2007-09-23 15:05 ` Richard Stallman
2007-09-23 16:11 ` Andreas Schwab
2007-09-24 18:20 ` Richard Stallman
2007-09-22 16:20 ` Dan Nicolaescu [this message]
2007-09-22 16:31 ` Michaël Cadilhac
2007-09-22 17:52 ` Dan Nicolaescu
2007-09-22 20:02 ` Stefan Monnier
2007-09-22 20:04 ` Stefan Monnier
2007-09-23 16:14 ` Dan Nicolaescu
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=200709221620.l8MGKeR4006966@oogie-boogie.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=rms@gnu.org \
--cc=schwab@suse.de \
/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.