2017-06-02 16:33:03 +0100, Geoff Clare: [...] > I'm fairly sure the intention is that only: > > sh [options]... -- - [operands]... > > is undefined, but it's been badly worded and thus also applies to other > cases that it obviously wasn't meant to cover. [...]
Thanks. But even then, what would be the rationale for that? Are there implementaions for which that "-" would be ignored or mean stdin (in which case I'd expect "sh - -" to also be a problem)? I can't find any. Does that mean that one can't do: sh -s -- "$@" << \EOF some code EOF as that may not work if "$1" is "-"? Same for sh -- "$script" args -- Stephane
