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

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

bug#2398: marked as done (23.0.90; MUSTMATCH read-file-name arg, confirm


From: Emacs bug Tracking System
Subject: bug#2398: marked as done (23.0.90; MUSTMATCH read-file-name arg, confirm-nonexistent-file-or-buffer)
Date: Sat, 15 Aug 2009 20:50:05 +0000

Your message dated Sat, 15 Aug 2009 16:43:23 -0400
with message-id <address@hidden>
and subject line Re: bug#2398 NOT FIXED - MUSTMATCH read-file-name arg, 
confirm-nonexistent-file-or-buffer
has caused the Emacs bug report #2398,
regarding 23.0.90; MUSTMATCH read-file-name arg, 
confirm-nonexistent-file-or-buffer
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact address@hidden
immediately.)


-- 
2398: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=2398
Emacs Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 23.0.90; MUSTMATCH read-file-name arg, confirm-nonexistent-file-or-buffer Date: Thu, 19 Feb 2009 16:02:44 -0800
1. Doc string of `read-file-name' says:
 
 "Fourth arg MUSTMATCH non-nil means require existing file's name.
  Non-nil and non-t means also require confirmation after completion."
 
A value such as `confirm-after-completion' does NOT mean that an
existing file name is required, AFAICT, so the first sentence is
false. Passing a value such as `confirm-after-completion' is no
guarantee that the string returned by `read-file-name' names an
existing file.
 
2. Similarly, the Elisp manual seems incorrect. You are not REQUIRED to
enter the name of an existing file, if MUSTMATCH is, say,
`confirm-after-completion'.  Completion is still lax in this case;
it's just that you must confirm that you want a non-existing file
name.
 
3. Beyond the fact that the doc is inaccurate (and confusing) on this
matter, the new behavior also breaks existing code. Any code that
passed a non-nil non-t value in order to guarantee that the value
returned by the function names an existing file is now broken.
 
4. The user option `confirm-nonexistent-file-or-buffer' is not even
documented in this regard in the Elisp manual.
 
5. The default value of `confirm-nonexistent-file-or-buffer' is
`after-completion', but if you do M-x customize-option
confirm-nonexistent-file-or-buffer you see "Always", not "After
completion", as the current value, and State says STANDARD. Something
is amiss here. Further, you can change the value, using the Value
Menu, to "Always" or to "After completion", but the actual value
remains the same: `after-completion'. This is a mess (bugged), and
quite confusing. And the available values don't seem to
correspond to either the documented completion behavior (see above) or
the actual completion behavior.
 
 
 
In GNU Emacs 23.0.90.1 (i386-mingw-nt5.1.2600)
 of 2009-02-01 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'
 




--- End Message ---
--- Begin Message --- Subject: Re: bug#2398 NOT FIXED - MUSTMATCH read-file-name arg, confirm-nonexistent-file-or-buffer Date: Sat, 15 Aug 2009 16:43:23 -0400 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
>> Any code that passed a non-nil non-t value in order to
>> guarantee that the value returned by the function
>> names an existing file is now broken.
>
> How will this problem be addressed? Will the regression be fixed? If
> not, will the new behavior at least be signaled to users as an
> incompatible change?

No further code changes will be made; and the change is already
documented in NEWS.

--- End Message ---

reply via email to

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