Arch Linux User Repository

This used to be the nvi-multibyte-upstream repository. If you still have nvi-multibyte-upstream installed remove it before installing from this repo as there will be conflicts.

@randiprit Yes, that is the email thread I was referring too. I had forgotten about the other reason (besides bugs) for not going to nvi2, namely, licensing issues, BSDs are usually very fussy about licenses. I don't know why Debian is not on nvi2 though.

Anyway, I don't have a strong opinion on this, whatever the maintainer does will be fine with me! :-)

@archdub maybe this is the email you refer to (6 years old): https://misc.openbsd.narkive.com/9NHoQv8L/nvi-and-unicode#post4

I use daily nvi2 without any stability problem, never crashed. The lack of 'expandtab' option in (Open)(n)vi(1) is a no-go for me.

@Invarianz: thank you for the tip.

Be sure that in no case I am trying to denigrate the (Open)(n)vi(1) version or trying discouraging it's use. I was just mentioning the existence of version 2. From now I will stop to pollute comments of this AUR Package.

nvi2 is the standard vi in FreeBSD (it's in base), however OpenBSD uses 1.79, NetBSD uses 1.81.6, Debian uses 1.81.6.

I remember reading a comment by the vi maintainer of OpenBSD. He was asked why not put nvi2 in base. He said because it has bugs. This was a few years back. Sorry, I don't have the url for this email, it should be somewhere in the archives.

My point it that not necessarily everyone prefers nvi2, so a possibility would be to create a new AUR package for nvi2 for people to have a choice.

Current maintainer of nvi(2) :

https://github.com/lichray/nvi2

Need its companion (DB1) from the BSD world :

https://github.com/matijaskala/db1

Arch repo dependencies :

cmake
libiconv
libbsd

My way of building nvi :

1.  git clone https://github.com/lichray/nvi2
2.  cd nvi2
3.  git clone https://github.com/matijaskala/db1
4.  cmake -DCMAKE_EXE_LINKER_FLAGS=-Ldb1 -DDB_INCLUDE_DIR=db1/include .
5.  make -C db1
6.  make

Then you can copy/move the executable anywhere in your path and invoke 'nvi'. Enjoy

This used to be the nvi-multibyte-upstream repository. If you still have nvi-multibyte-upstream installed remove it before installing from this repo as there will be conflicts.

Updated to the latest in git, use sha instead of md5.

# Maintainer: cmichi <mich [at] elmueller [dot] net>
#
# This package aims to provide the latest offical, upstream nvi
# with multibyte support enabled.

pkgname=nvi-multibyte-upstream
pkgdesc="Upstream nvi with enabled multibyte support"
arch=('x86_64')
url="git://repo.or.cz/nvi.git"
license=("BSD")
conflicts=("nvi")

_COMMIT="864873d3f353ab3e54040817ec562bd3b346b55f"
source=("http://repo.or.cz/nvi.git/snapshot/$_COMMIT.tar.gz")
sha256sums=('f3deecd2f24bf58c1bc2e7f6efcc9419493c1c3b52137ee86fbaee8c83807251')

# the last official release was 1.81.6, but there have been
# commits since then. hence i append the timestamp of the
# latest commit to the version number.
_COMMIT_HASH="${_COMMIT:0:7}"
pkgver=1.81.6_20200915

pkgrel=2

build(){
  cd "$srcdir"/nvi-$_COMMIT_HASH/dist/
  ./distrib
  cd ../build.unix

  ../dist/configure \
    --prefix="$pkgdir"/usr \
    --program-prefix=n \
    --enable-widechar # for multibyte support

  make
}

package(){
  cd "$srcdir"/nvi-$_COMMIT_HASH/build.unix

  make install

  # license
  install -Dm644 "$srcdir"/nvi-$_COMMIT_HASH/LICENSE \
          "$pkgdir"/usr/share/licenses/$pkgname/LICENSE
}

@ncoop Thanks for the suggestion! I updated the package.

PKGBUILD should provide or conflict with nvi.