Subject: Re: bin/4167: WIBNI sh supported file/command/etc completion?
To: der Mouse <mouse@Rodents.Montreal.QC.CA>
From: John Nemeth <jnemeth@cue.bc.ca>
List: current-users
Date: 09/27/1997 14:34:26
On Sep 26,  8:33pm, der Mouse wrote:
}
} >>> [sh already links with libedit]
} >> It does?  Hm, maybe that explains the major bloat in file size I
} >> encountered recently while recompiling.  Makes me want to submit a
} >> PR to compile it _out_.
} > Like I said, I think command editing/history is a POSIX
} > requirement...
} 
} So?

     I have to agree with der Mouse here.  Just ask me how much I care
about POSIX...

     In any event, not only is /bin/sh statically linked, it must go
on install/ERD's (Emergency Recovery Disk).  It really needs to be as
lean and mean as possible.  People that want all the fancy command
line type things that make interactive usage nicer can always use
bash.  Personally, I still use a csh for interactive usage.

}-- End of excerpt from der Mouse