Shawn Walker wrote:
> On 10/09/2007, Glenn Fowler <gsf at research.att.com> wrote:
> > On Mon, 10 Sep 2007 16:13:12 -0500 Shawn Walker wrote:
> > > On 10/09/2007, David Korn <dgk at research.att.com> wrote:
[snip]
> > bash also does this for
> >
> > echo foo:b<TAB><TAB>
> >
> > and will not match valid pathnames containing ':'
> >
> > why does bash do that?
>
> Apparently, it requires the ':' to be escaped, this works:
>
> mkdir foo:bar
>
> echo foo\:b<TAB><TAB>
>
> I suppose then it is down to the common case. Which is more common, a
> colon in a directory or filename or a colon being used as a list
> separator?
>
> I defer to whatever relevant standard exists, but it is something to
> think about...
What about adding something like .sh.ewfs ("ewfs"="editor word field
seperators") which works like IFS and contains the characters which are
delimiters for words in the current editor mode ? AFAIK it should allow
the implemenmtation of both ksh93 and bash behaviour by adding or
obmitting ':' from this list...
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) roland.mainz at nrubsig.org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
