From owner-freebsd-current@FreeBSD.ORG  Sun Aug 11 09:24:02 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 1033)
 id B9E82ADC; Sun, 11 Aug 2013 09:24:02 +0000 (UTC)
Date: Sun, 11 Aug 2013 09:24:02 +0000
From: Alexey Dokuchaev <danfe@FreeBSD.org>
To: Peter Wemm <peter@wemm.org>
Subject: Re: Fun with nvi
Message-ID: <20130811092402.GA47711@FreeBSD.org>
References: <CAGE5yCoOSKD9uaHT-FoGNZtO1yFzxMvow9A6ZpNgeoefRQBJxQ@mail.gmail.com>
 <20130811083529.GA20632@FreeBSD.org>
 <CAGE5yCq_bnW-E9gAPDgn71O7stdUA09TcS31N8Yge0-L6mJtTQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGE5yCq_bnW-E9gAPDgn71O7stdUA09TcS31N8Yge0-L6mJtTQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: FreeBSD Current <current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Aug 2013 09:24:02 -0000

On Sun, Aug 11, 2013 at 02:15:15AM -0700, Peter Wemm wrote:
> On Sun, Aug 11, 2013 at 1:35 AM, Alexey Dokuchaev <danfe@freebsd.org> wrote:
> > 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.

Yuck, pardon my typos: it should read "base vi(1)" and "has WIDECHAR option".

> > How is nvi 1.81.6 (per editors/nvi-devel) is different from nvi2, btw?
> 
> The original reason was that nvi-devel switched from the db-1.x API to
> db-3/db-4 which were sleepycat licensed, and are now Oracle.  It was a
> big chunk of code at the time.  eg:
> USE_BDB=                42+
> CONFIGURE_ARGS+=        --with-db-prefix=${LOCALBASE}
> 
> nvi2 is nvi-1.79 from base with a serious cleanup pass.  The
> iconv/multibyte code will look quite familiar if you've looked at the
> nvi-devel code, along with a cherry-picking of additions from nvi-m17n
> for better CJK/non-utf8 support.

Understood, thanks for the insight.

> nvi2 does not have the same level of sophisticated encoding detection
> that nvi-m17n has.

I don't care too much about encoding detection since all sane parts of the
world would have switched to UTF-8 by now. ;-)

./danfe