Re: tcsh (Re: Reducing KODRETRY)

On Thu, 11 Jan 2007, Steven W. Orr wrote:
>You may continue to use tcsh and I won't hold it against you. I am however 
>confidant that my reasoning for why you shouldn't is sound. I have no idea 
>what you do for a living but as a software engineer, I have found that 
>people in my profession tend to use things like their login shell and 
>their editor of choice all day long. My preference is to work with people 
>who are obvious power users of those components. Being a power user of a 
>shell that doesn't allow for subroutines is an oxymoron.

I'm a software engineer.  No, being a power user of a shell without subroutines
is not an oxymoron.

I use the shell for relatively simple things, piping, redirection and such.
Pipe text through cut and grep and paste, etc..  Anything more and I write a
program.

I am *slightly* annoyed once in a rare while about the inability to redirect
stdout and stderr separately, but that is greatly outweighed by the
inertia of using what I know, rather than re-learning how to do 
everything I already know in a slightly different way (env whatever test
instead of setenv whatever test, etc..)
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info