Re: TAB vs. colon

[jidanni]

>>>>> "JS" == Jon Seymour <jon.seymour@gmail.com> writes:
JS> You mean apart from the obvious that perhaps the user's intent was to
JS> paste unescaped colons into the command line at that point? In any
JS> case, paste is a function of the terminal, not the shell.
I'm saying normally when we build a path, we enter several TABS in the
process, and the \:  \: stuff gets added for us, so no problem.

But sometime we don't type in the path by hand, but instead paste it in
from elsewhere via the mouse or something. In this case we have to
painfully add the \   \ stuff by hand before any TAB expansion works.