From owner-freebsd-bugs@freebsd.org  Fri Mar 24 08:28:00 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1161D1B3F0
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Fri, 24 Mar 2017 08:28:00 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id A0ABD2F3
 for <freebsd-bugs@FreeBSD.org>; Fri, 24 Mar 2017 08:28:00 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2O8S0Cn068088
 for <freebsd-bugs@FreeBSD.org>; Fri, 24 Mar 2017 08:28:00 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 205697] vi gets confused and corrupts file being edited
Date: Fri, 24 Mar 2017 08:28:00 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.2-RELEASE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: alexander.klein@physiologie.med.uni-giessen.de
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-205697-8-jDnRQ4QZFf@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-205697-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-205697-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Mar 2017 08:28:00 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D205697

--- Comment #5 from Alexander Klein <alexander.klein@physiologie.med.uni-gi=
essen.de> ---
(In reply to Bjorn Robertsson from comment #4)

There are even more bugs which are probably related to the same problem:

Bug 196447 - vi(1) misbehavior when encountered invalid Unicode character
Bug 203040 - Nvi truncates files with non-ASCII characters

It seems to be possible to get the data back in a number of cases, even aft=
er
having written a corrupted file to disk:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D196447#c4

The issue as a whole seems to be quite involved, however:

https://github.com/lichray/nvi2/issues/12
http://lists.suckless.org/dev/1312/18786.html

--=20
You are receiving this mail because:
You are the assignee for the bug.=