Date: Sun, 16 Dec 2007 19:36:53 -0500 From: Chuck Robey <chuckr@chuckr.org> To: freebsd-questions@freebsd.org Subject: Re: Apparently, csh programming is considered harmful. Message-ID: <4765C4A5.4020906@chuckr.org> In-Reply-To: <20071216232830.GD5874@piglet.digitaltorque.ca> References: <20071214010542.GA19553@demeter.hydra> <20071214022529.GA2571@kobe.laptop> <4761F17F.9030908@chuckr.org> <20071214033333.GA3455@kobe.laptop> <20071216232830.GD5874@piglet.digitaltorque.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael P. Soulier wrote: > On 14/12/07 Giorgos Keramidas said: > >> Tcsh is a fine shell. I'm using it all the time (that's how I found out >> that a buglet reported by Kris Kennaway a few months ago was indeed a >> bug which I could reproduce too). > > I always found csh/tcsh aliases annoying, since there are no shell functions. > I also found the shell redirection awkward. There;s one item that is much more easily done in csh/tcsh than in the sh based ones .... that's redirecting the stderr along with the stdout. with tcsh, when I do a make, I commonly do a: make |& tee makeout which causes both the stdout and stderr files to be redirected to the "makeout" make listing file. I;'ve never figured out any reasonably simple way to do that in any sh-like shell. Is there any simble way that you know of? > > It's ok otherwise, but I've since become addicted to bash. Mind you, I'm sure > some tcsh users could point out some features that bash doesn't have. > > Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4765C4A5.4020906>