public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: Cygwin and x: directory
Date: Mon, 15 Jul 2013 11:20:00 -0000	[thread overview]
Message-ID: <CA+kUOans72pM2FUE9v=XNK6XBkyD1JMPsy9=5Pi5kesW155wyA@mail.gmail.com> (raw)
In-Reply-To: <20130715104018.GB18483@calimero.vinschen.de>

On 15 July 2013 11:40, Corinna Vinschen wrote:
> On Jul 12 20:09, Nellis, Kenneth wrote:
>> IMHO, this makes an interesting problem (unrelated to git):
>> Shell script prompts user for file name.
>> User enters "x:".
>> Script proceeds as follows:
>> $ mkdir tmpdir
>> $ touch tmpdir/x:
>> $ # useful work done here
>> $ rm -r tmpdir
>> rm: cannot remove `tmpdir/x:': No such file or directory
>> rm: cannot remove `tmpdir': Directory not empty
>> $
>
> That's a problem of how recursive rm works.  It chdir's into
> the subdirs it's working on and then calls "x:" which is recognized
> as drive prefix of a windows path.  `rm ./x:' works as expected.

Does that mean this is a bug in Cygwin rm that ought to be fixed
(subject to SHTDI), or that it's a limitation of Cygwin rm for which
the cure looks to be worse than the symptoms?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2013-07-15 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12 20:45 Nellis, Kenneth
2013-07-15 11:13 ` Corinna Vinschen
2013-07-15 11:20   ` Adam Dinwoodie [this message]
2013-07-15 11:41     ` Corinna Vinschen
2013-07-16  3:45   ` Andrey Repin

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+kUOans72pM2FUE9v=XNK6XBkyD1JMPsy9=5Pi5kesW155wyA@mail.gmail.com' \
    --to=adam@dinwoodie.org \
    --cc=cygwin@cygwin.com \
    /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.
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).