From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-16104-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 13577 invoked from network); 22 Oct 2001 11:27:23 -0000
Received: from sunsite.dk (130.225.247.90)
  by ns1.primenet.com.au with SMTP; 22 Oct 2001 11:27:23 -0000
Received: (qmail 467 invoked by alias); 22 Oct 2001 11:27:16 -0000
Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 16104
Received: (qmail 454 invoked from network); 22 Oct 2001 11:27:15 -0000
Date: Mon, 22 Oct 2001 07:27:13 -0400
From: Clint Adams <clint@zsh.org>
To: Geoff Wing <gcw@zsh.org>
Cc: Zsh Hackers <zsh-workers@sunsite.dk>
Subject: Re: multibyte backwarddeletechar
Message-ID: <20011022072713.A31806@dman.com>
References: <20011021114254.A17952@dman.com> <20011022105702.A4297@primenet.com.au> <20011021215022.A25491@dman.com> <20011022132306.A5808@primenet.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20011022132306.A5808@primenet.com.au>; from gcw@zsh.org on Mon, Oct 22, 2001 at 01:23:06PM +1000

> But what happens when I do, say, "history-incremental-search-backward",
> input characters for the second half a multibyte glyph, then do
> "kill-line"?  What happens when I do, "down-case-word" when we only
> consider byte by byte (which may easily corrupt the second byte of a
> two-byte glyph)?  These are a couple off the top of my head.

If the strings are being stored as wchar_t arrays, I don't think
these are problems.