Thanks for agreeing with the basic point (if we don't include "PERL",
we shouldn't include ksh93).

I never use file-complete.  I find it a ghastly feature, which is why
I pointed out that it has to be able to be turned off.

As for removing /bin/ksh altogether: Well, I've been toying with
the idea of setting my default shell to /bin/sh...  If you really
want to be minimalist, we should ditch /bin/csh, since it is no
longer actually required for anything (it used to be that the
external "which" command was a csh script, I believe, but someone
rewrote it; I think that that was the only place csh was required
in the base system---other than also being a default shell for
root).

But, getting back to /bin/ksh: How can you get arbitrary commands
to run in your prompt in /bin/sh?  E.g., here are two prompts; I'd
like to know how to do them (using general mechanisms) in /bin/sh:

     PS1='(`/bin/hostname`) `/bin/date "+%Y%m%d %H%M%S"` : `/bin/pwd`| '

     PS1='Cap: `/bin/df . | /usr/bin/awk '"'"'/%/{print $5}'"'"'` `pwd`| '

(Sorry for the ugly quoting in the second one.)

That's one thing that I know, offhand, that I use in /bin/ksh but which
doesn't seem to exist in /bin/sh.

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