Subject: Re: echo weirdness
To: None <>
From: Christian Biere <>
List: current-users
Date: 02/19/2004 00:22:30
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

David Laight wrote:
> On Tue, Feb 17, 2004 at 04:44:18PM +0100, Christian Biere wrote:
> > manpage refers to echo(1) but /bin/echo doesn't understand '-e'. Isn't
> > this a doc-bug? Also /bin/sh doesn't use getopt-style parsing for the
> Do not put your fingers into a bag of worms - they bite :-)

Rumour has it they're kind of nutritious, though. ;-)
> Basically echo is required to be broken for compatibility.
> In particular BSD echo and SYSV echo are irreparably incompatible, and
> neither is (or can be made) getopt compatible.

Well, I just think that even the weirdest behaviour is acceptable as
long as it's documented. The hint to use printf instead of echo if in
doubt would be a worthwhile addition, too.


Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.2.4 (NetBSD)