Re: lib/56926: curses: vi screen corrupted with UTF-8 multicolumn characters

[David Holland <dholland-bugs%netbsd.org@localhost>]

The following reply was made to PR lib/56926; it has been noted by GNATS.

From: David Holland <dholland-bugs%netbsd.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: lib/56926: curses: vi screen corrupted with UTF-8 multicolumn
 characters
Date: Thu, 6 Oct 2022 22:42:11 +0000

 (this message didn't get sent to gnats originally)
 
    ------
 
 From: Rin Okuyama <rokuyama.rk%gmail.com@localhost>
 To: lib-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
 Cc: Brett Lymn <blymn%NetBSD.org@localhost>
 Subject: Re: lib/56926: curses: vi screen corrupted with UTF-8 multicolumn
 	characters
 Date: Fri, 15 Jul 2022 23:38:33 +0900
 
 On 2022/07/15 22:50, rokuyama.rk%gmail.com@localhost wrote:
 > % ftp http://www.netbsd.org/~rin/curses_20220715/sample.txt
 > ...snip...
 > % export LC_CTYPE=ja_JP.UTF-8
 > % locale
 > LANG=""
 > LC_CTYPE="ja_JP.UTF-8"
 > LC_COLLATE="C"
 > LC_TIME="C"
 > LC_NUMERIC="C"
 > LC_MONETARY="C"
 > LC_MESSAGES="C"
 > LC_ALL=""
 > % vi sample.txt
 
 Oops, this example is misleading. This is on SSH session with
 unicode-aware terminal emulators.
 
 If you reproduce the problem on xterm, LC_CTYPE should be set
 *before* you start xterm.
 
 Thanks,
 rin