Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!tut.cis.ohio-state.edu!docboy.cs.mun.ca!jeff1
From: jeff1@docboy.cs.mun.ca (Jeff Sparkes)
Newsgroups: gnu.bash.bug
Subject: slight readline modification
Message-ID: <8911152057.AA14292@docboy>
Date: 15 Nov 89 17:27:32 GMT
References: <8911151711.AA18794@hub.ucsb.edu>
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 39

Brian Fox writes:
 >    >>>>> 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.
 > 

	Oops.  It certainly does sound like I'm saying I wrote the
undo stuff.  Sorry about that.  I have added undoable undos, though,
but not sent them to Brian yet. He, of course, has done the bulk of
bash/readline work; I just hacked in some vi stuff.  Steven did say
that he liked vi mode though.
	NOTE: it appears that Brian is rabidly anti-vi.  Me, I live in
both worlds, but had gotten used to vi in ksh, so I decided to add it
to vi.

 >    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

It doesn't.  Sort of makes sense to me that it should be at the end,
but ksh didn't do it that way.