[Bug 196447] vi(1) misbehavior when encountered invalid Unicode character

2015-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196447 --- Comment #5 from lich...@gmail.com --- Although not resolving this issue, FYI, the patch to prevent file truncation upon writing is merged: https://github.com/lichray/nvi2/commit/310d1e86c0b3db7f7e025e3092afc78e3d906fa2 -- You are re

[Bug 196447] vi(1) misbehavior when encountered invalid Unicode character

2015-01-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196447 --- Comment #6 from lich...@gmail.com --- (In reply to Xin LI from comment #5) The default action is horrible, I agree. Not a locale problem. I explained the tab issue before, it's my fault, because I bound the filename completion key to

[Bug 196447] vi(1) misbehavior when encountered invalid Unicode character

2015-01-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196447 --- Comment #5 from Xin LI --- (In reply to lichray from comment #4) Well, depends on how we define it. I think the editor should not "eat" file contents :) Yes, I think the editor should ask the user and reject edits if it's not possible

[Bug 196447] vi(1) misbehavior when encountered invalid Unicode character

2015-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196447 --- Comment #4 from lich...@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

[Bug 196447] vi(1) misbehavior when encountered invalid Unicode character

2015-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196447 --- Comment #3 from Xin LI --- (In reply to lichray from comment #2) Well, data corruption is much more serious than merely not having search working. I think vi should probably ask the user whether they want to reload the file in 'C' loc

[Bug 196447] vi(1) misbehavior when encountered invalid Unicode character

2015-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196447 --- Comment #2 from lich...@gmail.com --- (In reply to Xin LI from comment #0) Forgot to answer your original question: why the search does not go across the first defected line. The whole story is much worse than this: if you write the fi

[Bug 196447] vi(1) misbehavior when encountered invalid Unicode character

2015-01-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196447 --- Comment #1 from lich...@gmail.com --- (In reply to Xin LI from comment #0) We know these types of issues for quite a long time, but I don't have a desired behavior in mind. For now, the workaround would be to set the correct locale: