On 11/09/2007, Roland Mainz <roland.mainz at nrubsig.org> wrote: > 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...
As I said, something configurable would work. I am curious as to why bash requires you to escape the ':' while ksh does not. That's an interesting design decision on both sides... -- Shawn Walker, Software and Systems Analyst binarycrusader at gmail.com - http://binarycrusader.blogspot.com/ "Beware of bugs in the above code; I have only proved it correct, not tried it. " --Donald Knuth