> 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 <*blabl
"[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
