Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 17 Apr 2002 10:03:53 +0100 Message-ID: <936-Wed17Apr2002100353+0100-starksb@ebi.ac.uk> From: David Starks-Browning MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Chris Metcalf Cc: cygwin@cygwin.com Subject: Re: bash 2.05a-3: option to allow drive letter prefixes for completion? In-Reply-To: References: <020416180646.AA13793.SM@nike.ins.cwru.edu> On Tuesday 16 Apr 02, Chris Metcalf writes: > On Tue, 16 Apr 2002, Chet Ramey wrote: > > Readline has a set of characters it uses as word > > delimiters for completion, and the calling application can modify that > > set to its tastes. Bash includes `:' as a word break character, which > > makes it convenient to complete colon-separated lists like $PATH. > > Since the colon breaks words, the only thing that gets passed to the > > filename completer is `/' and whatever follows it. Quoting the colon > > (the simplest thing to use is a backslash) causes readline to not > > consider it a word break character. > > In that case, it sounds like the right question to be asking is whether > there is a user-visible knob that we can tweak to modify the set of > characters which bash passes to readline as word break characters. > Both ":" and "@" seem like reasonable candidates to allow removing > from the word-break list, with the obvious caveats about functionality > that would no longer be supported within the shell: $PATH-type list > modification and automatic hostname completion, respectively. Fair enough, but that would be an issue for bash, not Cygwin. Since it's probably only a source of confusion for Cygwin users, I'll add something to the Cygwin FAQ about this. Thanks Chet, for helping us out with the answer! Regards, David (Cygwin FAQ maintainer) -- 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/