Re: [hackers] [vis] [PATCH] fix {, }, (, ) movements

From: Markus Teich <markus.teich_AT_stusta.mhn.de>
Date: Wed, 3 Feb 2016 11:49:25 +0100

Marc André Tanner wrote:
> Did you also consider implementing text_paragraph_{next,prev} by skipping to
> actual content i.e. a loop while (c == '\n' || c == '\r') followed by a call
> to text_line_empty_{next,prev}?

Good idea putting that text_line_empty_next function to use. Updated patch will
be ready soon. On the way I noticed another little glitch:

When opening a file where the amount of lines fit exactly on your screen and you
use `G` (or any other movement that would jump to the end of the file), the
cursor ends up in the second column of the last line instead of (what I think
should be the behaviour) scrolling down and placing the cursor one line below.
This is probably not related to movement code at all. I think it is related to
the fact that the position after the last character in a file is still
addressable with vis.

--Markus
Received on Wed Feb 03 2016 - 11:49:25 CET