On Thu, Sep 07, 2023 at 08:04:43AM BST, Walter Alejandro Iglesias wrote:
> Dear OpenBSD developers,
> 
> On Aug 2 I reported this bug:
> 
>   https://marc.info/?l=openbsd-bugs&m=169100763926909&w=2
> 
> After fiddling around I found a solution that works for both vi base and
> nvi from ports:
> 
>   https://marc.info/?l=openbsd-bugs&m=169269999218514&w=2
> 
> Since nobody answered me in bugs@ I sent a message to ports@ and Cc:
> Anthony J. Bentley who told me to contact Zhihao Yuan, nvi developer
> upstream.  I don't use github, I don't have a github account, luckily
> after searching the web I found an email address of Zhihao.  He
> understood the issue and answered me with what seems to be a more
> consistent patch:
> 
>   https://marc.info/?l=openbsd-bugs&m=169277277928008&w=2
> 
> Which, needless to say, also works for both. vi on base and nvi on
> ports.  Below I paste a cvs version of Zhihao's patch to use it with vi
> on base.
> 
> So it only rests some OpenBSD developer here to take look.  It's not
> going to take up much of your time, everything has already been chewed
> up :-).

Hi Walter,

This isn't related to the bug per se but it might be useful bit of
information regardless.

The nvi port is actually nvi2[0], which is based on the original
(read Keith Bostic's) nvi, where, in turn, the base vi(1) comes
from.

The original nvi is still maintained[1] by Sven Verdoolaege[2] so
you might want to give him a shout, too.

[0] https://github.com/lichray/nvi2
[1] https://repo.or.cz/nvi.git
[2] 
https://sites.google.com/a/bostic.com/keithbostic/the-berkeley-vi-editor-home-page

Regards,

Raf

Reply via email to