Re: [PATCH] new shopt `colonbreakswords' for bash 3.0

> While the current behavior of filename completion (treating
> the colon `:' as a separator for words to be completed) is
> useful for PATH style variables, it is sometimes irritating
> for users working a lot with filenames that contain a colon.
> 
> This patch makes this configurable with a new shopt
> `colonbreakswords', enabled by default. It can be unset with

Why not just use $COMP_WORDBREAKS?  That's what it's there for.  One
problem with it, however, is that it's not initialized with the
`standard' list of break characters, so you have to play around with
it.  Let me know about problems you find. 

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
                                                Live...Laugh...Love
Chet Ramey, ITS, CWRU    chet@xxxxxxxxxxx    http://tiswww.tis.cwru.edu/~chet/