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

Previous Next

Full log

View this message in rfc822 format

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: 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.

Previous Next

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