From owner-freebsd-current@FreeBSD.ORG Sun Aug 11 08:35:29 2013 Return-Path: Delivered-To: current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1033) id B6CF447F; Sun, 11 Aug 2013 08:35:29 +0000 (UTC) Date: Sun, 11 Aug 2013 08:35:29 +0000 From: Alexey Dokuchaev To: Peter Wemm Subject: Re: Fun with nvi Message-ID: <20130811083529.GA20632@FreeBSD.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Aug 2013 08:35:29 -0000 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