Re: bin/57072: nvi error "Error: move: l(24 + 0) c(80 + 0)"

[Simon Burge <simonb%NetBSD.org@localhost>]

The following reply was made to PR bin/57072; it has been noted by GNATS.

From: Simon Burge <simonb%NetBSD.org@localhost>
To: Rin Okuyama <rokuyama.rk%gmail.com@localhost>,
    Brett Lymn <blymn%internode.on.net@localhost>
Cc: gnats-bugs%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
    netbsd-bugs%netbsd.org@localhost
Subject: Re: bin/57072: nvi error "Error: move: l(24 + 0) c(80 + 0)"
Date: Wed, 26 Oct 2022 19:40:40 +1100

 Rin Okuyama wrote:
 
 > On 2022/10/26 6:18, Brett Lymn wrote:
 > > On Tue, Oct 25, 2022 at 09:52:59PM +0900, Rin Okuyama wrote:
 > >>
 > >> I'm not sure whether nvi is not guilty here, but it seems that nvi hits
 > >> a curses bug or its undefined behavior.
 > >>
 > > 
 > > I will have a look, writing to the bottom right corner can be...
 > > complicated.  It depends on a lot of things.  Thanks for the debug, I
 > > will sort through it and see what I can work out.
 >
 > Thank you for your help! And yes, it seems to depend precisely on
 > situations. I tried to write a simplified code to reproduce the
 > problem, but I couldn't...
 
 I haven't looked closely at the vi code, but would be easier/simplier
 or just plain more-hacky to just not try to put the cursor in the last
 column of the last row?  Already it deals with status messages longer
 than (window-width) chars by doing a multiline status message, so maybe
 just tweak that logic to kick in for (window-width - 1)?
 
 Or Brett can fix a complicated scenario :).
 
 Cheers,
 Simon.