Interactive /bin/sh

Alex de Kruijff akruijff at dds.nl
Mon Dec 16 01:49:48 UTC 2013


Warren Block schreef op 16-12-2013 2:00:
> On Sun, 15 Dec 2013, Ian Lepore wrote:
>
>>> If just those 2 features would be implemented, I would be completely 
>>> into /bin/sh
>>
>> An alternate viewpoint:  I would prefer that /bin/sh remain as lean and
>> mean as possible, conforming to posix and especially NOT becoming
>> bloated with interactive usability stuff.  If you want a user-friendly
>> bourne shell and can afford the memory and cycle bloat, use bash.
>
> An alternate, alternate viewpoint: the code that keeps the command 
> history is already there, adding code that searches through it for 
> completion would probably not make it significantly larger.  So the 
> cost is small.
>
> If people want to use it as their main shell, that's fine. Personally, 
> I would just like it to make things easier and faster when only sh is 
> available.  The command history was a good step in that direction.

There are proberly al lot of features that would come with low cost on 
there own, but it all adds up. I personaly give preference to tcsh and 
only use sh for shell programming.


More information about the freebsd-hackers mailing list