Date: Wed, 21 Oct 1998 22:07:50 +0200 From: "Jeroen C. van Gelderen" <gelderen@mediaport.org> To: <freebsd-current@FreeBSD.ORG> Subject: echo behaviour Message-ID: <00b701bdfd2e$7b29c5a0$1400000a@deskfix.local>
next in thread | raw e-mail | index | archive | help
Hallo, Today I stumbled on the problem of building a 'cross-platform' shell script for the sh shell. I noticed that the /bin/echo behaves differently then the sh built-in echo in reacting to the "\c" escape. FreeBSD sh accepts "\c" only when the -e flag is specified. FreeBSD /bin/echo accepts "\c" always and does not accept the -e flag Solaris sh accepts "\c" always and does not accept the -e flag Linux' built-in echo accepts "\c" only when the -e flag is specified. Why the inconsistency between the sh built-in and /bin/echo? Is it on purpose? If so, shouldn't the man-page be updated to reflect the inconsistency? If it's not on purpose: is conforming to the opengroup 'Single UNIX' considered a good idea? I'll patch if neccessary, please tell me what -if any- I should patch... Last but not least: is this the correct list? Cheers, Jeroen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00b701bdfd2e$7b29c5a0$1400000a>