GNU bug report logs - #23743
24.5; Opening output file: invalid argument, .../foo-<-4-n.el

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 23743 in the body.
You can then email your comments to 23743 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.5; Opening output file: invalid argument, .../foo-<-4-n.el
Date: Fri, 10 Jun 2016 10:35:54 -0700 (PDT)

emacs -Q

C-x C-f foo-<-4-n.el

Type some text in that file buffer.

C-x C-s  ; try to save it.

Saving file d:/usr/drew/drews-lisp-20/foo-<-4-n.el...
basic-save-buffer-2: Opening output file: invalid argument, d:/.../foo-<-4-n.el

Apparently it doesn't like `<' in a file name?  If so, and if that is
"normal", then the user should get a much better error message than
this.

(Same problem in the latest Emacs 25 build I have.)



In GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/usr --host=i686-pc-mingw32'

Message #8 received at 23743 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 23743 <at> debbugs.gnu.org
Subject: Re: bug#23743: 24.5;
 Opening output file: invalid argument, .../foo-<-4-n.el
Date: Fri, 10 Jun 2016 22:04:23 +0300

> Date: Fri, 10 Jun 2016 10:35:54 -0700 (PDT)
> From: Drew Adams <drew.adams <at> oracle.com>
> 
> emacs -Q
> 
> C-x C-f foo-<-4-n.el
> 
> Type some text in that file buffer.
> 
> C-x C-s  ; try to save it.
> 
> Saving file d:/usr/drew/drews-lisp-20/foo-<-4-n.el...
> basic-save-buffer-2: Opening output file: invalid argument, d:/.../foo-<-4-n.el
> 
> Apparently it doesn't like `<' in a file name?

Yes, Windows doesn't allow that.

> If so, and if that is "normal", then the user should get a much
> better error message than this.

That's the error that comes from the filesystem, Emacs doesn't know
any better.

Message #11 received at 23743 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> users.sourceforge.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 23743 <at> debbugs.gnu.org, Drew Adams <drew.adams <at> oracle.com>
Subject: Re: bug#23743: 24.5;
 Opening output file: invalid argument, .../foo-<-4-n.el
Date: Mon, 20 Jun 2016 23:15:07 -0400

On Fri, Jun 10, 2016 at 3:04 PM, Eli Zaretskii <eliz <at> gnu.org> wrote:
>> Date: Fri, 10 Jun 2016 10:35:54 -0700 (PDT)
>> From: Drew Adams <drew.adams <at> oracle.com>
>>
>> Apparently it doesn't like `<' in a file name?
>
> Yes, Windows doesn't allow that.
>
>> If so, and if that is "normal", then the user should get a much
>> better error message than this.
>
> That's the error that comes from the filesystem, Emacs doesn't know
> any better.

Right, cf https://support.microsoft.com/en-us/kb/177506

Is it worth blocking this sort of file name in read-file-name, or
should we just mark this wontfix?

Message #14 received at 23743 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Noam Postavsky <npostavs <at> users.sourceforge.net>
Cc: 23743 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: Re: bug#23743: 24.5;
 Opening output file: invalid argument, .../foo-<-4-n.el
Date: Tue, 21 Jun 2016 15:48:53 +0300

> From: Noam Postavsky <npostavs <at> users.sourceforge.net>
> Date: Mon, 20 Jun 2016 23:15:07 -0400
> Cc: Drew Adams <drew.adams <at> oracle.com>, 23743 <at> debbugs.gnu.org
> 
> Right, cf https://support.microsoft.com/en-us/kb/177506
> 
> Is it worth blocking this sort of file name in read-file-name

No, I don't think so, because MS-Windows includes a pluggable
filesystem design, whereby any 3rd party filesystem device driver
could be added, which supports these characters in file names.  We
simply cannot know up front which filenames are invalid.

> or should we just mark this wontfix?

I think so, yes.

Thanks.

Message #21 received at 23743 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: 23743 <at> debbugs.gnu.org, tracker <at> debbugs.gnu.org
Subject: RE: bug#23743 acknowledged by developer (control message for
 bug 23743)
Date: Wed, 7 Dec 2016 10:30:55 -0800 (PST)

So was it fixed? closed as wont-fix? Why doesn't this notification say
what the closing status is?

Sure, someone can look up the bug thread at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23743, but why should s?he need to?

> This is an automatic notification regarding your bug report
> #23743: 24.5; Opening output file: invalid argument, .../foo-<-4-n.el,
> which was filed against the emacs package.
> 
> Thank you for your report, which has now been closed.
> You can view the full report at
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23743
> 
> If you require further information, please followup to
> 23743 <at> debbugs.gnu.org.
> 
> debbugs.gnu.org maintainers
> (administrator, GNU bugs database)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.