Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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:	Tue, 16 Apr 2002 12:45:38 -0400 (EDT)
From:	Chris Metcalf <metcalf AT incert DOT com>
To:	cygwin AT cygwin DOT com
Subject:	bash 2.05a-3: option to allow drive letter prefixes for completion?
Message-ID:	<Pine.LNX.4.44.0204161239130.30266-100000@rd.incert.com>
MIME-Version:	1.0

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 -- InCert Software -- 1 (617) 621 8080
                metcalf AT incert DOT com -- http://www.incert.com/~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/

- Raw text -