🚀 go-pugleaf

Never saw the original article but this has been quoted several times.

! If both these questions have solutions already it only shows that tcsh 
! has too many features.  I can't remember them so I don't use them.

'scuse me?  I've probably forgotten more about the shell than I know.  Hell,
I don't even remember what that little knob on the side of my toaster is for.
I like my toast the way it comes out so why mess with it, although I'm sure
some pop-tart junkie is really happy the knob is there.

Having lots of features is what I consider a 'rich' environment.  This is
opposed to a 'gui' environment, of which it's been said 'Gui's make simple
things easier, and hard things impossible.'  If you're any good at all then
someday you'll be glad some nameless soul added that obscure feature to
tcsh.  And if you're smart you'll put that obscure feature into your .login
or .cshrc so you don't have to re-learn it.

Excuse the Gui slam but a few months ago I spent a week on a Mac.  It would
have been a day had anybody known how to get straight to the hardware a-la
Dos's mode command or the SunOS /etc/remote file.  What I needed was
non-standard, thus Apple decided I didn't need to do it.  I've also had bad
experiences with CASE tools, where the vendor got so wrapped up in his mouse
he forgot that all I wanted to do was get my job done.

Excuse the Mac slam, but that wasn't a pleasant experience :-(

If you think tcsh has too many features then forget about ever learning perl.

jim

-- 
Lawyers Creed:  What's mine is mine, what's yours is negotiable.
--------------------------------------------------------------
Jim Harkins                         [ucsd|uunet]!pacdata!jim
Pacific Data Products               jim@pacdata.com
--------------------------------------------------------------