On Thu, Feb 17, 2011 at 9:10 PM, Andreas Schwab <sch...@linux-m68k.org>wrote:
> "Clark J. Wang" <dearv...@gmail.com> writes:
>
> > On Thu, Feb 17, 2011 at 6:19 PM, Andreas Schwab <sch...@linux-m68k.org
> >wrote:
> >
> >> "Clark J. Wang" <dearv...@gmail.com> writes:
> >>
> >> > On Thu, Feb 17, 2011 at 5:00 PM, Andreas Schwab <
> sch...@linux-m68k.org
> >> >wrote:
> >> >
> >> >> "Clark J. Wang" <dearv...@gmail.com> writes:
> >> >>
> >> >> > I think char `:' is not special in bash.
> >> >>
> >> >> $ printf "%q\n" "$COMP_WORDBREAKS"
> >> >> $' \t\n"\'><=;|&(:'
> >> >>
> >> >>
> >> > I don't think that explain the issue.
> >>
> >> /* characters that need to be quoted when appearing in filenames. */
> >> rl_filename_quote_characters = " \t\n\\\"'@<>=;|&()#$`?*[!:{~";
> >> /*}*/
> >>
> >>
> > So that's problem. I don't think @=: need to be treated specially. Any
> > reason?
>
> They are used as word break characters during completion.
>
>
That's the way it's implemented but that does not mean that's reasonable.
> Andreas.
>
> --
> Andreas Schwab, sch...@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>
