> "GH" == Geir Hauge writes:
GH> A workaround would be to quote the path. E.g. instead of
GH> ls u
GH> do
GH> ls ''u
KoOl! It's a deal and I withdraw my case. Let's just hope this tip is
documented.
2011/12/30
> 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.
>
A workaround would be to quote the path. E.g. instead of
ls u
do
> "JS" == Jon Seymour 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 severa
