Date: Sun, 11 Aug 2013 08:35:29 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Peter Wemm <peter@wemm.org> Cc: FreeBSD Current <current@freebsd.org> Subject: Re: Fun with nvi Message-ID: <20130811083529.GA20632@FreeBSD.org> In-Reply-To: <CAGE5yCoOSKD9uaHT-FoGNZtO1yFzxMvow9A6ZpNgeoefRQBJxQ@mail.gmail.com> References: <CAGE5yCoOSKD9uaHT-FoGNZtO1yFzxMvow9A6ZpNgeoefRQBJxQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Aug 10, 2013 at 10:33:20AM -0700, Peter Wemm wrote: > I've been tinkering with the nvi refresh from the GSoC in 2011, aka nvi2. > > https://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1 > https://github.com/lichray/nvi2 > > The goal was to update the multibyte handling in nvi-1.79 (the one we > have in our tree) in such a way we could import it. Yes, please do something about our base(1) being unable to talk in anything non-ASCII. I'm using editors/nvi-devel now, which was WIDECHAR option, and was wondering why those changes were never imported into the base. How is nvi 1.81.6 (per editors/nvi-devel) is different from nvi2, btw? ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130811083529.GA20632>