RE: /bin/sh: wildcard expansion fails

[[EMAIL PROTECTED]@mgedv.net]

 Incidentally, it is operating as documented (pathname expansion isn't
 listed as performed on redirection targets), and explicitly allowed by
 the POSIX standard.

but /bin/sh could accept *txt until there's more than one file matching
after expansion. if that's the case, an error like *blabla: invalid
argument
could be raised.

not that i see this as a real problem, it's just a convenience-thing ;-)


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: /bin/sh: wildcard expansion fails

[Lowell Gilbert]

[EMAIL PROTECTED]@mgEDV.net [EMAIL PROTECTED] writes:

 i know things like cat *lst|wc, but i don't want to type them.
 when i try to use wildcards with  or  in /bin/sh, it fails:

 my input (only one file with this name exists in the current dir):
 wc *lst

Which is equivalent to wc *lst, so I'm not sure why you'd want to do
that... 

 /bin/sh's output:
 cannot open *lst: No such file or directory

 is there a way to configure /bin/sh for more/better expansion?

No.

Incidentally, it is operating as documented (pathname expansion isn't
listed as performed on redirection targets), and explicitly allowed by
the POSIX standard.

 btw, with csh it works fine ;-)

And some other shells too, I'm sure.  

Feel free to fix this yourself; if it still meets the POSIX standards
(i.e., still errors out if the expansion returns multiple files), the
change would probably be accepted...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]