Re: [PATCH] latest ash has broken 'echo' command
On Fri, 22 Oct 1999, Anthony Towns wrote:
> Then the Single Unix Specification is broken, and we shouldn't follow
> it. Seriously, -e and -n are expected features of echo on GNU/Linux
> systems, no matter what the Single Unix Spec might or might not say.
In any case we need some standardisation on "echo" behaviour.
- should echo understand options?
- should echo default to interpret escaped characters?
- what escape characters are there and what is their interpretation?
> Dropping them shortly before freeze seems an insane thing to do too,
Can achieving consistency across all echo implementations be harmful to
the pending release?