Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mit-eddie!snorkelwacker!tut.cis.ohio-state.edu!HUB.UCSB.EDU!bfox%vision
From: bfox%vision@HUB.UCSB.EDU (Brian Fox)
Newsgroups: gnu.bash.bug
Subject: slight readline modification
Message-ID: <8911151711.AA18794@hub.ucsb.edu>
Date: 15 Nov 89 17:10:16 GMT
References: <JEFF1.89Nov15122619@docboy.mun.edu>
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: bfox%cornu@hub.ucsb.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 33


   Posted-Date: 15 Nov 89 12:26:19 GMT
   Date: 15 Nov 89 12:26:19 GMT
   From: garfield!stretch!jeff1@uunet.uu.net  (Jeff Sparkes)
   Organization: Memorial University of Newfoundland
   References: <1989Nov14.063818.17288@fxgrp.fx.com>
   Sender: bug-bash-request@prep.ai.mit.edu

   >>>>> On 14 Nov 89 06:38:18 GMT, grady@fxgrp.fx.com (Steven Grady) said:

   grady> First thing I want to say is that I'm way impressed with the
   grady> input editing features of bash (ie the readline library).  I'm
   grady> very appreciative of the work that went into making a good vi
   grady> mode, especially.  And it even has multiple undo!  Now, on to
   grady> the suggestions...

   Actually, multiple undos are a sort of side effect.  Both multiple and
   vi style will be in my next bunch.  I've even added undoable undos.

You are VI fixated.  He is complementing the fact that Readline has
multiple undos.  For those who don't know, Jeff wrote the bulk of the
vi mode.

   grady> I currently use tcsh, and one thing it does that bash's
   grady> readline doesn't is put the cursor at the _end_ of the line
   grady> when you start moving through the history (in either vi or
   grady> emacs mode).  Having the cursor at the end is slightly
   better

This is simply false.  The cursor moves to the end of the line in
emacs mode.  Perhaps it doesn't do this in vi-mode?

Brian