X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=n4IY/iVkvCQxdENizpFrrnTlTWbm8qe/rbonrSv9lE5xYfJH2+uoj ZWhQNUfZLEbB4ic4WmHVAehy85Wb7P5I6BC2/tIqjKqaFdZfLI0/U5VtJDOwFhbS SkSw1YdTut0G3ZbYWYkdsbpDVNAhP8qAXnaKDoTuNinXIhY4tBsWa8= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=2LZVvE0uWMFDbOVIStdTruP3EzI=; b=qqoB+a+YFlr5j9it59593D1hVKqX Tk32GaR4465/Qq/yYHEnTE+w4alSeqmqLegPn5DIkKN/j1wFFQw5t86gOnewt/ST l9D3ftzy/hi3w6B4nyMUREQSO4cqm2VRba+N8btWQ4/6E3S6WmY+yAaxdE2HQgsV W+ieNjgDbZ0f1t8= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_40,RDNS_NONE autolearn=no version=3.3.1 Date: Mon, 15 Jul 2013 13:13:47 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Cygwin and x: directory Message-ID: <20130715111347.GC18483@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <0D835E9B9CD07F40A48423F80D3B5A7021D8E0FC AT USA7109MB022 DOT na DOT xerox DOT net> <20130715104018 DOT GB18483 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- 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