Re: [9fans] Shall we fix the use of Up/Dn arrows?

[erik quanstrom <quanstro@quanstro.net>]

> > nothing to do with the concept of a line delimited by newlines. For
> > the movement, such delimited lines are completely irrelevant. For the
> > movement there is no difference whether there is a newline on the
> > previous visible line or the line was broken due to the width of the
> > window.
> >
> > What I speak about is 'as if' clicking the mouse up one visible line.
> >

> How would you go about doing that?

> There's no cursor based addressing available in the screens. And good
> riddance too, methinks.

and

> what if the current selection is a block of text? anyway, I don't
> think acme really knows where your pointer is (in x,y coords). I could
> be wrong, though

acme, sam, rio use frame(2).  frcharofpt(2) and frptofchar(2)
convert between characters and cartesian coordinates.
to find the closest character in the next line you're going to
have to start at the beginning of the line and add character
widths until the next character puts you past your target.
this requires a bit of work, since the text is stored in a different
data structure.

please use the up/down arrows in vim for a few minutes with
code and think about how many special cases there are.  for
example, you'll notice that vim stores an ideal x coordinate
for arrowing.

now if you still think this is such a great idea....
go forth and code!  or don't.  either way, let's pick a different
topic.

- erik