From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 23743@debbugs.gnu.org
Subject: bug#23743: 24.5; Opening output file: invalid argument, .../foo-<-4-n.el
Date: Tue, 21 Jun 2016 15:48:53 +0300 [thread overview]
Message-ID: <83lh1y7lmy.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-8zXHvtKeVgfwO=SPCxUkqkFuWmWK+wnkmOxEd7wiu7-Q@mail.gmail.com> (message from Noam Postavsky on Mon, 20 Jun 2016 23:15:07 -0400)
> 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.
prev parent reply other threads:[~2016-06-21 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 17:35 bug#23743: 24.5; Opening output file: invalid argument, .../foo-<-4-n.el Drew Adams
2016-06-10 19:04 ` Eli Zaretskii
2016-06-21 3:15 ` Noam Postavsky
2016-06-21 12:48 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lh1y7lmy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23743@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).