From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 20119@debbugs.gnu.org
Subject: bug#20119: 25.0.50; tramp-test30-special-characters hangs on Cygwin
Date: Tue, 17 Mar 2015 17:31:32 +0200 [thread overview]
Message-ID: <83sid3y71n.fsf@gnu.org> (raw)
In-Reply-To: <873853ptq5.fsf@gmx.de>
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: kbrown@cornell.edu, 20119@debbugs.gnu.org
> Date: Tue, 17 Mar 2015 15:46:26 +0100
>
> >> (file-exists-p "~/ file name with spaces ")
> >> => t
> >>
> >> (file-exists-p "~/ file name with spaces")
> >> => t
> >>
> >> (directory-files "~/")
> >> => (" file name with spaces" ...)
> >
> > Where do you see errors in primitives here? They are just
> > peculiarities of the underlying filesystem.
> >
> > Like I said: such file names should be avoided, but they are not
> > disallowed.
>
> I do not believe it is important, but in my naive feeling
> "~/ file name with spaces " and "~/ file name with spaces" are different.
>
> Especially, since leading spaces in file names are treated:
>
> (file-exists-p "~/file name with spaces ")
> => nil
The Win32 file-name related APIs "normalize" whitespace, and this is
the result. The only way to work around this is bypass the Win32
layer altogether, and work on lower levels, where many nice features
of Win32 need to be done by hand. Too much trouble for too small a
gain, IMO.
prev parent reply other threads:[~2015-03-17 15:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 16:21 bug#20119: 25.0.50; tramp-test30-special-characters hangs on Cygwin Ken Brown
2015-03-16 16:37 ` Ken Brown
2015-03-16 19:05 ` Michael Albinus
2015-03-16 20:22 ` Ken Brown
2015-03-16 16:39 ` Michael Albinus
2015-03-16 16:47 ` Ken Brown
2015-03-18 19:53 ` Michael Albinus
2015-03-18 20:10 ` Eli Zaretskii
2015-03-18 21:06 ` Michael Albinus
2015-03-18 21:02 ` Ken Brown
2015-03-18 21:09 ` Michael Albinus
2015-03-16 17:08 ` Eli Zaretskii
2015-03-16 18:56 ` Michael Albinus
2015-03-16 19:32 ` Eli Zaretskii
2015-03-17 11:11 ` Michael Albinus
2015-03-17 12:15 ` Eli Zaretskii
2015-03-17 14:46 ` Michael Albinus
2015-03-17 15:31 ` 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=83sid3y71n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20119@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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).