[indiana-discuss] scope

Keith Bierman Keith.Bierman at Sun.COM
Tue Aug 7 23:31:36 PDT 2007


On Aug 7, 2007, at 6:28 PM, Tim Bray wrote:

>
> I'm a little out of touch with ksh, never used it much.  But here are
> a list of things that a plurality if not a majority of developers
> coming over from Linux are going to expect to work, and regard it as
> a bug if they don't.
>
> 1. !!
> 2. bg/fg
> 3. control-R to search through history
> 4. up-arrow/down-arrow Just Work with history
> 5. pushd/popd
> 6. autocomplete on tab
> 7. %1
>

bash being a merge of sorts of ksh and csh clearly has an edge on  
this feature list ;>

My informal survey suggests that Linux and Mac defaults tend to be  
bash these days (a few hours installing Fedora to add to my Ubuntu  
samples, and all my macs with one exception seem to have defaulted  
that way (I suspect the outlier was configured oddly by me and long  
since forgotten ;>)

So if the goal is to make not yet Solaris users maximally at home,  
shouldn't the default be bash?

> 1. !!
originally csh, not ksh
> 2. bg/fg
originally ksh
> 3. control-R to search through history
> 4. up-arrow/down-arrow Just Work with history
configurable, but not the default as far as I know
> 5. pushd/popd
originally csh not ksh
> 6. autocomplete on tab
not quite, but close
> 7. %1
??? I don't know what this means in bash either (just the usual job  
control, %n for getting to backgrounded jobs?).

Default doesn't mean only; and I can't imagine not having ksh (of  
some flavor, or multiple flavors). Agnostic about what to specify for  
"official" scripting. Happy for it to remain ksh.
>

Keith H. Bierman    keith.bierman at Sun.COM   |  khbkhb at gmail.com
Strategic Engagement Team                   | AIM:  
kbiermank                |
<speaking for myself, not Sun*> Copyright 2007






More information about the indiana-discuss mailing list