[ On Tuesday, May 3, 2005 at 17:38:50 (-0500), Richard Rauch wrote: ]
> Subject: Re: Tab completion in /bin/sh
>
> As for removing /bin/ksh altogether: Well, I've been toying with
> the idea of setting my default shell to /bin/sh...

Before you do that you might want to consider that (pd)ksh is smaller
(at least on some platforms, like this alpha):

	$ size /bin/*sh
	text    data    bss     dec     hex     filename
	420304  22400   24212   466916  71fe4   /bin/ksh
	457546  17976   21604   497126  795e6   /bin/sh

(that's from 1.6.x, btw, and of course they're both static-linked)

>  If you really
> want to be minimalist, we should ditch /bin/csh,

Yup -- I did so long ago!  :-)

> since it is no
> longer actually required for anything (it used to be that the
> external "which" command was a csh script

Yes, because "which" is a csh feature that ((pd)k)sh users should not be
using ever at all -- the proper true sh equivalent is "type".

> But, getting back to /bin/ksh: How can you get arbitrary commands
> to run in your prompt in /bin/sh?

Probably, but you shouldn't -- there are better ways to get useful
information about your current session status.  :-)

(and keep in mind that arbitrary length prompts screw up command-line
editing somewhat too)

For example see all the fun in my ksh setup files in:

	ftp://ftp.weird.com/pub/local/dotfiles.tar.gz

(note that they work with most any functional shell too!  :-)

-- 
						Greg A. Woods

H:+1 416 218-0098  W:+1 416 489-5852 x122  VE3TCP  RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>          Secrets of the Weird <woods@weird.com>