From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7236 invoked from network); 21 Oct 2001 17:13:51 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 21 Oct 2001 17:13:51 -0000 Received: (qmail 28225 invoked by alias); 21 Oct 2001 17:13:44 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 16091 Received: (qmail 28210 invoked from network); 21 Oct 2001 17:13:42 -0000 From: Bart Schaefer Message-Id: <1011021171339.ZM14059@candle.brasslantern.com> Date: Sun, 21 Oct 2001 17:13:38 +0000 In-Reply-To: <20011021114254.A17952@dman.com> Comments: In reply to Clint Adams "multibyte backwarddeletechar" (Oct 21, 11:42am) References: <20011021114254.A17952@dman.com> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.dk Subject: Re: multibyte backwarddeletechar MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Oct 21, 11:42am, Clint Adams wrote: } } This causes backward-delete-char to delete entire } multibyte characters (valid in the current locale) } rather than their component octets. I'm a bit surprised that this wouldn't cause significant confusion in the ZLE display code. How did the multi-byte character get input in the first place? Is it displayed as occupying one character position on the screen, or several? If only one, doesn't the cursor end up in the wrong place on most word- or line-oriented motions that cross it? If we're going to support wide and/or multi-byte characters, I think we should Do It Right, not by pasting a zillion workarounds into individual editor functions. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net