Date: Wed, 14 Mar 2001 17:35:39 +0300 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: David Malone <dwmalone@maths.tcd.ie> Cc: Christos Zoulas <christos@zoulas.com>, tcsh-bugs@mx.gw.com, current@FreeBSD.ORG Subject: Re: tcsh 6.10.00 echo;echo;echo; bug with fix Message-ID: <20010314173539.A73652@nagual.pp.ru> In-Reply-To: <200103141410.aa44559@salmon.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Wed, Mar 14, 2001 at 02:10:06PM %2B0000 References: <20010314155908.A72442@nagual.pp.ru> <200103141410.aa44559@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 14, 2001 at 14:10:06 +0000, David Malone wrote: > Will it change what happens if you do: > > set null="" > echo $null > > (this produces nothing in "traditional" tcsh and csh)? It will change. > I guess we should leave it up to the tcsh folks. There are other > internal csh commands which behave differently to external commands > (nice and time come to mind). I think it is known that 'echo ""' is > a relatively portable way of printing a blank line. echo is more like as external command, even in its internal form it tends to be compatible even with SysV-isms. What non-BSD grown (i.e. SysV) csh echo prints? -- Andrey A. Chernov http://ache.pp.ru/ 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?20010314173539.A73652>