Re: [vile] Odd cursor problem after hitting end of file

[Chris Green]

On Sun, Feb 19, 2006 at 06:46:19PM -0500, Thomas Dickey wrote:
> On Fri, Feb 17, 2006 at 02:45:56PM +0000, Chris Green wrote:
> > I have recently noticed an odd problem which occurs after hitting
> > end-of-file with the cursor.
> > 
> > If you 'j' (next-line) to the end of a file, leaving the cursor at the
> > start of the line then, when you move the cursor back up again it's at
> > the end of every line.  This is very annoying when you just 'bounce'
> > off the end of a file and then go back up again as, with long lines,
> > the display flickers all over the place.
> > 
> > I'm running "xvile version 9.5 for solaris2.6", I don't think this
> > happened with the last few previous versions.
> 
> I'm not seeing _that_ (literally just 'j' and 'k').
> 
> But if you do a '$' to go to the end of the line before starting the j/k,
> it will do this.  (I agree that it's odd that vile will track to the
> end of all lines after that, but iirc, it's done that "forever", since
> vi does this).
> 
What you describe is what vile used to do for me.

If you take the cursor explicitly to the end of the line and then j/k
up  and down the file then the cursor stays at the end of whatever
line you stop at.  However if the cursor is at the start of the line
when you j/k then it stays at the start of the line.

What I'm seeing is that the cursor takes itself to the end of the line
whenever you hit end-of-file or start-of-file.  It doesn't happen
actually when you hit the end/start, the cursor stays at the start of
the line until you j/k away from the end, then it immediately goes to
the end of the line next to the start/end line.  This is only
happening on my Solaris builds of vile, it happens on both vile and
xvile though.

-- 
Chris Green (address@hidden)

    "Never ascribe to malice that which can be explained by incompetence."