unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 20119@debbugs.gnu.org
Subject: bug#20119: 25.0.50; tramp-test30-special-characters hangs on Cygwin
Date: Tue, 17 Mar 2015 12:11:27 +0100	[thread overview]
Message-ID: <87k2yfanfk.fsf@gmx.de> (raw)
In-Reply-To: <83r3sozqjd.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 16 Mar 2015 21:32:54 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Michael Albinus <michael.albinus@gmx.de>
>> Cc: kbrown@cornell.edu,  20119@debbugs.gnu.org
>> Date: Mon, 16 Mar 2015 19:56:25 +0100
>> 
>> It could be also the case that it is an error in file name primitives on
>> w32.
>
> Could be, but at least "C-x C-f" will happily create such files.

One case on w32 I could reproduce is the following: There is just one
special file "~/ file name with spaces ". The first test is OK, the
other two tests not (wrong handling of trailing spaces)

(file-exists-p "~/ file name with spaces ")
=> t

(file-exists-p "~/ file name with spaces")
=> t

(directory-files "~/")
=> (" file name with spaces" ...)

Best regards, Michael.





  reply	other threads:[~2015-03-17 11:11 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 [this message]
2015-03-17 12:15           ` Eli Zaretskii
2015-03-17 14:46             ` Michael Albinus
2015-03-17 15:31               ` Eli Zaretskii

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=87k2yfanfk.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=20119@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).