-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Paul Eggert on 3/20/2006 11:58 PM: >>> There's a little history here. POSIX 1003.2-1992 said that echo has >>> implementation-defined behavior if given any options, or if any >> Are you sure about "any option"? The current spec only talks about -n. > > Yes, I have the printed copy of POSIX 1003.2-1992, and it has > different wording in this area.
POSIX 1003.1-2001 states on line XCU 12820 that "Implementations shall not support any options." When compiled for xpg (or using shopt -s xpg_echo), both -e and -n should therefore be literal strings, not options. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEKSSB84KuGfSFAYARAgAdAJ9+a44hUziPgLECYgtvGv9TAlxAfACfcQGx 0BvRfNt7iLLX5CLa4zkpq94= =QQky -----END PGP SIGNATURE----- _______________________________________________ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash