Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!tut.cis.ohio-state.edu!sbphy.ai.mit.edu!bfox
From: bfox@sbphy.ai.mit.edu (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: bash bug report
Message-ID: <9001042050.AA01880@sbphy.Ucsb.EDU>
Date: 4 Jan 90 20:50:46 GMT
References: <3749@convex.UUCP>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: bfox@ai.mit.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 33


   Date: 7 Dec 89 17:18:52 GMT
   From: sun-barr!newstop!texsun!convex!tchrist%convex.COM@ames.arc.nasa.gov  (Tom Christiansen)
   Organization: CONVEX Software Development, Richardson, TX
   References: <8912030428.AA01426@kailand.kai.com>
   Sender: bug-bash-request@prep.ai.mit.edu

   In article <8912030428.AA01426@kailand.kai.com> pwolfe@kailand.kai.com (Patrick Wolfe) writes:

   >I would like to commend all those who've been working on bash and readline so
   >far.  I plan to continue using bash, and to try to find and fix any bugs I can.
   >The "vi mode" simply blows away TCSH.

   Well, it's nice, but it's not as complete a vi as ksh's vi mode, 
   which is too bad.

It would be more helpful to tell us what features are missing in Bash.
Then perhaps we could put them in.

   I also like the way tcsh allows ^W to back up to things like / and +,
   not just to white space.

The command <backward-kill-word> operates in this fashion.  You can
set C-w to run this command in your ~/.inputrc file with:

	C-w: backward-kill-word

   And I miss the asynchronous notification of tcsh and csh that's also
   lacking in ksh.

Try putting "notify=" in your ~/.bashrc file.

Brian