[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#23743: 24.5; Opening output file: invalid argument, .../foo-<-4-n.el
From: |
Eli Zaretskii |
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@users.sourceforge.net>
> Date: Mon, 20 Jun 2016 23:15:07 -0400
> Cc: Drew Adams <drew.adams@oracle.com>, 23743@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.