Before people get too starry eyed over the AT&T ksh, I'd point out that
I've had some problems when trying to settle into an AT&T ksh.  I.e.,
it's not a superset of our /bin/ksh.

I don't remember the exact problems.  I'd personally be unhappy about
such a change.

As long as I can turn tab completion off, I wouldn't object to
tab-completion being added.  (More than once, in BASH, I have
pressed tab for some reason and found the shell seizes up for
several seconds while building a possible completion list---a list,
I might add, that I didn't want in the first place.)

If people want a better programming language than /bin/sh and awk,
I'd suggest importing Python (for style) or "PERL" (for pragmatism)
rather than AT&T ksh.  (^&  Python is a really cool language, and
there is actually some "PERL" code involved in building X as I recall.


Just my 2.718281828459045... cents' worth.

-- 
  "I probably don't know what I'm talking about."  http://www.olib.org/~rkr/