Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Message-Id: <5.1.0.14.2.20020416100842.00ae53b8@pop3.cris.com>
X-Sender: rrschulz@pop3.cris.com
Date: Tue, 16 Apr 2002 10:11:14 -0700
To: Chris Metcalf <metcalf@incert.com>, cygwin@cygwin.com
From: Randall R Schulz <rrschulz@cris.com>
Subject: Re: bash 2.05a-3: option to allow drive letter prefixes for
  completion?
In-Reply-To: <Pine.LNX.4.44.0204161239130.30266-100000@rd.incert.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Chris,

I have a symbolic link in my Cygwin root for each drive on my system (e.g., 
/c -> /cygdrive/c). Completion in BASH recognizes these symlinks and 
follows them (without expanding it to the target).

Randall Schulz
Mountain View, CA USA


At 09:45 2002-04-16, Chris Metcalf wrote:
>Currently, if you use completion on a path with a drive letter (e.g. "ls 
>-d c:/win<TAB>"), bash considers the drive letter to be unrelated syntax 
>and expands out of the mounted root instead (e.g. c:/cygwin). This is 
>quite understandable and defensible, but it would be nice to allow drive 
>letters to be considered part of the path name if the user so chooses.  In 
>defense of this option, I submit:
>
>  * If I enter "ls -d c:/win*", the shell *does* include the drive
>    letter prefix as part of the path, and globs corrects (to c:/winnt).
>
>  * tcsh (6.11.00-4) by default does filename completion including
>    drive letter prefixes.
>
>Thanks for your consideration.
>
>                 Chris Metcalf


--
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/