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

[Oliver Eikemeier]

Chet Ramey wrote:

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

Uhm, yes, this would work. OTOH this will also influence
rl_filename_quote_characters, which has only cosmetic consequences,
but is irritating nevertheless.

If FreeBSD we have a lot of patch files that follow the naming tradition
of perl: replacing directory separators (slashes) by double colons. With
this patch filename completion works `like I would expect'. This might be
a very particular point of view, but digging through the debian bug
database I got the impression that others might share it.

Anyway, since it's easy to do, off by default and makes me happy
(although I admit the consequences are only optical) I guess it's a nice
thing to have. Or do I miss a way to influence the quoting along with the
word breaks?

Btw, thanks for the feedback
-Oliver