GNU bug report logs -
#3969
23.0.96; Cannot use File > Visit New File on MS Windows
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Sun, 02 Aug 2009 23:13:11 +0800
with message-id <4A75AD07.20904 <at> gnu.org>
and subject line Re: bug#3969: 23.0.96; Cannot use File > Visit New File on MS Windows
has caused the Emacs bug report #3969,
regarding 23.0.96; Cannot use File > Visit New File on MS Windows
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 help-debbugs <at> gnu.org
immediately.)
--
3969: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3969
Emacs Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
emacs -Q
Choose menu item File > Visit New File
You get the Windows `Find file:' dialog box. Enter the name of a new
file, e.g. `xxxx.txt', in field `File name:' and click button
`Open'. You get this error dialog box:
Find file:
xxxx.txt
File not found.
Please verify the correct file name was given
[OK]
In GNU Emacs 23.0.96.1 (i386-mingw-nt5.1.2600)
of 2009-07-09 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'
[Message part 3 (message/rfc822, inline)]
Drew Adams wrote:
> emacs -Q
>
> Choose menu item File > Visit New File
>
> You get the Windows `Find file:' dialog box. Enter the name of a new
> file, e.g. `xxxx.txt', in field `File name:' and click button
> `Open'. You get this error dialog box:
>
> Find file:
>
> xxxx.txt
> File not found.
> Please verify the correct file name was given
>
> [OK]
>
The bug was caused by the change that introduced confirmation for
partial completions in the minibuffer - now the MUSTMATCH arg to
read-file-name is not simply nil or non-nil, it can have other special
values too, which mean confirm rather than prevent entry of non-existent
files.
But none of the file dialogs were updated for these special values, so
x-file-dialog is still treating any non-nil value as "require an
existing file". The problem these special values try to prevent does
not really apply to file dialogs, so I have checked in a change that
treats them as nil when calling x-file-dialog.
This bug report was last modified 14 years and 349 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.