Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: multibyte backwarddeletechar

X-seq: zsh-workers 16104
From: Clint Adams <clint@xxxxxxx>
To: Geoff Wing <gcw@xxxxxxx>
Subject: Re: multibyte backwarddeletechar
Date: Mon, 22 Oct 2001 07:27:13 -0400
Cc: Zsh Hackers <zsh-workers@xxxxxxxxxx>
In-reply-to: <20011022132306.A5808@xxxxxxxxxxxxxxx>; from gcw@xxxxxxx on Mon, Oct 22, 2001 at 01:23:06PM +1000
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <20011021114254.A17952@xxxxxxxx> <20011022105702.A4297@xxxxxxxxxxxxxxx> <20011021215022.A25491@xxxxxxxx> <20011022132306.A5808@xxxxxxxxxxxxxxx>

> 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.

References:
- multibyte backwarddeletechar
  - From: Clint Adams
- Re: multibyte backwarddeletechar
  - From: Geoff Wing
- Re: multibyte backwarddeletechar
  - From: Clint Adams
- Re: multibyte backwarddeletechar
  - From: Geoff Wing

Messages sorted by: Reverse Date, Date, Thread, Author