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

[Brett Lymn <blymn%internode.on.net@localhost>]

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

From: Brett Lymn <blymn%internode.on.net@localhost>
To: Rin Okuyama <rokuyama.rk%gmail.com@localhost>
Cc: Simon Burge <simonb%NetBSD.org@localhost>, RVP <rvp%SDF.ORG@localhost>, gnats-bugs%netbsd.org@localhost
Subject: Re: bin/57072: nvi error "Error: move: l(24 + 0) c(80 + 0)"
Date: Thu, 27 Oct 2022 16:44:25 +1030

 On Thu, Oct 27, 2022 at 11:14:20AM +0900, Rin Okuyama wrote:
 > 
 > Yes, this works around the problem at the moment.
 > 
 > Although, the real fix should be to
 > - fix curses bug, or
 
 well, I said this was complicated, see PR#56224 where the behaviour
 changed.  Admittedly the previous behaviour was wildly wrong but the
 logic to return ERR if a wrapping function cannot wrap makes sense sort
 of.  Unfortunately susV2 is not really clear on how this should be
 handled.  It is interesting that this works with ncurses, if you follow
 the email trail there was a claim made that ncurses returned ERR in this
 situation too - perhaps that has changed?
 
 > - stop nvi from relying on undefined behavior of curses.
 > 
 
 I don't know if it is deliberate or not but it seems like nvi almost
 gets this right, it does a addstr of "." in the last column - if this
 addstr was an insch then things would be ok.  I used this in the slk
 support to write to the bottom right character, the last character is
 done as a insch which does not advance the cursor so will not cause a
 scroll and hence avoids the whole problem.
 
 -- 
 Brett Lymn
 --
 Sent from my NetBSD device.
 
 "We are were wolves",
 "You mean werewolves?",
 "No we were wolves, now we are something else entirely",
 "Oh"