X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 21 Sep 2009 21:33:40 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: [1.7] recursive /cygdrive problem Message-ID: <20090921193340.GN20981@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4AB1031D DOT 1050802 AT shaddybaddah DOT name> <4AB10645 DOT 9040401 AT cygwin DOT com> <4AB10A7F DOT 2090404 AT shaddybaddah DOT name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AB10A7F.2090404@shaddybaddah.name> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Sep 17 01:55, Shaddy Baddah wrote: > Hi Larry, > > Larry Hall (Cygwin) wrote: >> >> >> >>> Genuine bug? >> >> No, a feature. Having the existing drives show up under '/cygdrive' >> is a convenience >> for things like bash and other shells so that they can do completion >> on the paths to >> these drives. If you don't want what's under the '/cygdrive' >> directory, you can omit >> it from your invocation of 'find'. >> > > Respectfully, I think you've misunderstood my problem. I've just > posted a followup which will show an out and out inconsistency (well, > at least in my opinion): > > Shaddy AT x-vista ~ > $ ls /cygdrive/c/software/cygwin/cygdrive > > Shaddy AT x-vista ~ > $ cd /cygdrive/c/software/cygwin/ > > Shaddy AT x-vista /cygdrive/c/software/cygwin > $ ls ./cygdrive > c d e > > Shaddy AT x-vista /cygdrive/c/software/cygwin > $ > > IMO, the result of the first ls is the more logical. It at least is > consistent with 1.5 if anything else (not that this is a strong > argument). It's a bug nevertheless. I introduced it in May, when I tried to workaround a problem with a stored cwd using non-ASCII chars in case the application switches the locale. The idea was to store the path only as Windows path and evaluate the matching posix path only on first usage. Unfortunately that results in an unwanted side-effect: $ cd /cygdrive/c/cygwin $ pwd / I fixed this problem now differently. When setlocale is called, the path of the current working dir is actually converted from the old charset to the new charset. Thanks for the report, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader 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