emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-bug-tracker] bug#7777: closed (24.0.50; incompatible change for `


From: GNU bug Tracking System
Subject: [Emacs-bug-tracker] bug#7777: closed (24.0.50; incompatible change for `directory-abbrev-alist' not in NEWS)
Date: Fri, 07 Jan 2011 15:55:02 +0000

Your message dated Fri, 07 Jan 2011 18:01:34 +0200
with message-id <address@hidden>
and subject line Re: bug#7777: 24.0.50; incompatible change for 
`directory-abbrev-alist' not in NEWS
has caused the GNU bug report #7777,
regarding 24.0.50; incompatible change for `directory-abbrev-alist' not in NEWS
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
7777: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7777
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.0.50; incompatible change for `directory-abbrev-alist' not in NEWS Date: Mon, 3 Jan 2011 11:49:07 -0800
In Emacs 22, the doc string of `directory-abbrev-alist' says this:
 
"*Every* FROM string should start with `^'."
 
Now it says this:
 
*Every* FROM string should start with "\\`".
 
That means that *Every* existing customization is broken (or at least
contradicts the "should").  This incompatible change should be
mentioned in the NEWS.

In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
 of 2010-12-20 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.4) --no-opt --cflags
-Ic:/imagesupport/include'
 




--- End Message ---
--- Begin Message --- Subject: Re: bug#7777: 24.0.50; incompatible change for `directory-abbrev-alist' not in NEWS Date: Fri, 07 Jan 2011 18:01:34 +0200
> From: "Drew Adams" <address@hidden>
> Cc: <address@hidden>
> Date: Mon, 3 Jan 2011 20:12:33 -0800
> 
> > How about if we change the doc string to not sound like a stringent
> > requirement, but rather as a "note"?
> 
> That would be an improvement, thanks (the manual, likewise).

I fixed it on the emacs-23 branch (revision 100362).

> It would also help to explain why.  Explaining why helps avoid any
> misunderstanding wrt the older "rule", and it helps understand the new "note".

I added a short explanation.

> The other part of this bug is the location of the manual entry: Why the Elisp
> manual?  This is a user option.  If we feel it is important to tell users 
> about
> this in a manual, why wouldn't the Emacs manual be the right one?

Its description in the ELisp manual is due to the fact that the same
node describes the abbreviate-file-name function, which uses this
variable.  As for repeating the description in the user manual, I'm
not sure this variable is important enough.  So I left this part out
of the bugfix.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]