Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Wed, 25 Sep 2002 16:39:55 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin and short windows filenames (Was RE: Open bash at the current explorer directory?) Message-ID: <20020925203955.GC6078@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i On Wed, Sep 25, 2002 at 03:33:01PM -0400, Igor Pechtchanski wrote: >You're right, this is a problem. Cygwin should be able to handle >windows short form of directory names just as well as the long ones... >For some reason it doesn't ('cd /cygdrive/c/PROGRA~1' results in "cd: >/cygdrive/c/PROGRA~1: No such file or directory"). This is happening >in most shells (sh, bash, tcsh), so I'm assuming it's a 'chdir()' >problem. This only seems to happen if "check_case:strict" is part of >$CYGWIN. Passing a short windows filename to other programs, e.g., vi, >also fails with check_case:strict and succeeds with >check_case:relaxed/adjust. It's not really surprising that this would fail with strict case checking. If you look at the code for strict case checking then you'll see that there is no provision for doing a "It failed this check, I'd better check the short name, too". In fact, since strict case checking is supposed to make cygwin behave slightly more like UNIX, which has no such thing as a short name, then you could call this a feature. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/