Re: [PATCH] latest ash has broken 'echo' command
> So? That only proves that some (I'm not saying which) implementations of
> echo are flakey. It does not disprove the argument that I made.
It merely supports the argument that expecting an echo builtin to conform
to some unspecified standard is presumptuous.
SUS (and POSIX, AFAIAT) mandate the behavior of the 'command' builtin.
/etc/init.d/xdm contains the line
if command -v parse-xf86config > /dev/null 2>&1; then
ash and bash support this just fine, but zsh's 'command' builtin
has a different syntax.
Some people link /bin/sh to zsh. zsh does not claim to be
POSIX-compliant in this respect. The init script will break
(and subtly, too, since stderr is nulled). Should people be
using zsh as /bin/sh under Debian? Absolutely not. Do they?
Yes. Should zsh support options to 'command'? Maybe. Is it
a bug that zsh's behavior is different? No.
Reply to: