Hello.
Rich wrote: [snip]
Is it the shell that expands the * or is it the command? I guestimate would be the shell
> is expanding it. :)
It's the shell.
[snip]
We actually live on ksh and not bash. I feel that is the root of all my nightmares. :)
ksh should expand stuff like "*_*" the same way.
I think they're mostly compatible, but bash has some extensions that are non-POSIX, I think. IIRC that's mostly to do with variable expansion rather than wildcards. The bash manual is probably a better source of compatibility information than my memory, though.
(Puts on his flame-proof trousers.)
It could be worse. You could be using csh or tcsh. 8)
(Takes off his flame-proof trousers.)
Just curious...
Would you know how to get rid of that annoying 80 col line limit in ksh.
I've been searching and searching, asking anyone technical enough to
know. Just when we think we have it, nope. I looked at a lot of the
stty options compared Linux to the SGI and Solaris machines we run.
[snip]
Don't know anything about that.
Bye, Rich =]
-- Richard Dawe [ http://homepages.nildram.co.uk/~phekda/richdawe/ ]
"You can't evaluate a man by logic alone." -- McCoy, "I, Mudd", Star Trek
_______________________________________________ Bug-fileutils mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-fileutils
