Date: Wed, 14 Mar 2001 15:46: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: <20010314154636.A72329@nagual.pp.ru> In-Reply-To: <20010314124109.A30970@salmon.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Wed, Mar 14, 2001 at 12:41:09PM %2B0000 References: <20010313131944.A961@nagual.pp.ru> <20010313125249.704743330@hrothgar.gw.com> <20010314124109.A30970@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 14, 2001 at 12:41:09 +0000, David Malone wrote: > On Tue, Mar 13, 2001 at 07:52:49AM -0500, Christos Zoulas wrote: > > > Thanks so much! I wonder how come this bug remained unnoticed for such > > a long time! > > AFAIK, this isn't a bug. It's what csh has always done. (It's what > IBM and Sun's csh do anyway...) To echo a newline in csh you do > 'echo ""'. If this bug is rotten in csh as designed, it not means that it isn't the bug. Lets look from other side: "echo" is internal csh command which replace /bin/echo for speed reasons. /bin/echo;/bin/echo;/bin/echo produce 3 \n, so internal command must do the same in any case. -- 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?20010314154636.A72329>