As a side note, I find modern bash to be a very suitable replacement for ksh. I switched years ago, and I was a heavy Korn Shell user/programmer, a long-time holdout on learning this newfangled "Perl" thing because the KornShell Command and Programming Language was more than sufficient, thankyouverymuch.
It follows that my personal ksh environment was heavily customized, so I had to modify it somewhat to make it bash-friendly (main culprits: array syntax, unsupported typeset options, "print", "whence", coprocesses.) It was worth the effort, IMO, since every OS comes with bash these days, while ksh's price tag/license led to slower adoption among open source OSes (and pdksh has never risen to the level of the real thing). I've been quite happy with bash overall, and it might suit your needs as well. -- Mark J. Reed <[EMAIL PROTECTED]> -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
