From owner-freebsd-arch  Mon Jul  9 11:17:28 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103])
	by hub.freebsd.org (Postfix) with ESMTP id 57CFC37B406
	for <arch@freebsd.org>; Mon,  9 Jul 2001 11:17:25 -0700 (PDT)
	(envelope-from fenner@research.att.com)
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26])
	by mail-green.research.att.com (Postfix) with ESMTP
	id AC4971E83A; Mon,  9 Jul 2001 14:17:20 -0400 (EDT)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46])
	by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id OAA07556;
	Mon, 9 Jul 2001 14:17:16 -0400 (EDT)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost)
	by windsor.research.att.com (8.8.8+Sun/8.8.5) id LAA16879;
	Mon, 9 Jul 2001 11:17:16 -0700 (PDT)
Message-Id: <200107091817.LAA16879@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: ticso@mail.cicely.de
Subject: Re: nvi maintainer?
Cc: arch@freebsd.org
References:  <200107072203.PAA09299@windsor.research.att.com> <xzp3d88s3o0.fsf@flood.ping.uio.no> <20010708005155.J8775@canonware.com> <20010708032002.D97456@bohr.physics.purdue.edu> <20010709150739.A23210@cicely20.cicely.de>
Date: Mon, 9 Jul 2001 11:17:16 -0700
Versions: dmail (solaris) 2.2g/makemail 2.9a
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-arch.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-arch>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-arch>
X-Loop: FreeBSD.ORG


>What is wrong with nvi?

Two things that are wrong with what we have:
- "vi -r" failures, such as "failed to recover line NNNN".  I think this
  is the bug that Keith says required DB3 to fix.
- Dumping core when the information about the user running vi goes away
  between starting vi and making the first change requiring creation of
  a recovery file (see FreeBSD PR 3170).

I run into the first one way too often.  The second one isn't much of a
problem for me any more since our NIS servers at AT&T are pretty reliable.

  Bill

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message