From owner-freebsd-bugs@FreeBSD.ORG Mon Jan 5 21:51:43 2015 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D81A7398 for ; Mon, 5 Jan 2015 21:51:43 +0000 (UTC) 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 BF84E3628 for ; Mon, 5 Jan 2015 21:51:43 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t05LphxI078690 for ; Mon, 5 Jan 2015 21:51:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 196447] vi(1) misbehavior when encountered invalid Unicode character Date: Mon, 05 Jan 2015 21:51:43 +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: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: lichray@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2015 21:51:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196447 --- Comment #4 from lichray@gmail.com --- (In reply to Xin LI from comment #3) It's not quite "data corruption", since an error will be shown, and your data is not immediately lost: just switch to the correct encoding (at runtime, after the error is shown) with ":se fe=iso-8859-1" and write again then your data is back. Reload the file, like, as if ":e"? Sounds interesting. Added to the github issue. But I need to implement the raw-write first, otherwise the data is really lost. The change itself does not solve the problem. For example, when you open a slightly larger file, and the conversion error is close to the end of the file, then during your editing no error is shown (the conversion is only needed when the line is needed); the error only happens when writing. -- You are receiving this mail because: You are the assignee for the bug.