Date: Wed, 21 Oct 1998 16:34:55 -0400 (EDT) From: Chuck Robey <chuckr@mat.net> To: "Jeroen C. van Gelderen" <gelderen@mediaport.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: echo behaviour Message-ID: <Pine.BSF.4.05.9810211634140.375-100000@picnic.mat.net> In-Reply-To: <00b701bdfd2e$7b29c5a0$1400000a@deskfix.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 21 Oct 1998, Jeroen C. van Gelderen wrote: > 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... You really ought to search the mailing list archives, this has been beaten to death quite often ... ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- 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?Pine.BSF.4.05.9810211634140.375-100000>