Re: Fun with nvi

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_at_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