This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin and x: directory
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 15 Jul 2013 13:13:47 +0200
- Subject: Re: Cygwin and x: directory
- References: <0D835E9B9CD07F40A48423F80D3B5A7021D8E0FC at USA7109MB022 dot na dot xerox dot net> <20130715104018 dot GB18483 at calimero dot vinschen dot de> <CA+kUOans72pM2FUE9v=XNK6XBkyD1JMPsy9=5Pi5kesW155wyA at mail dot gmail dot com>
- Reply-to: cygwin at cygwin dot com
On Jul 15 12:00, Adam Dinwoodie wrote:
> 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?
It's a limitation in Cygwin itself.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple