From: Geoff Wing <gcw@zsh.org>
To: Zsh Hackers <zsh-workers@sunsite.dk>
Cc: Clint Adams <clint@zsh.org>
Subject: Re: multibyte backwarddeletechar
Date: Mon, 22 Oct 2001 13:23:06 +1000 [thread overview]
Message-ID: <20011022132306.A5808@primenet.com.au> (raw)
In-Reply-To: <20011021215022.A25491@dman.com>; from clint@zsh.org on Sun, Oct 21, 2001 at 09:50:22PM -0400
Clint Adams <clint@zsh.org> typed:
:For one thing, the %D escape in my prompt is substituted with
:multibyte glyphs in the relevant locales. That in itself
:poses a potential width calculation problem even if the user
:doesn't input any multibyte characters.
I understand a lot of the limitations, having programmed from both
ends of the system (output to a terminal and interpret such output
in a terminal emulator). And your initial list covers the basic
areas: deleting characters, basic cursor movement
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.
There'll be quite a few more and I think they'd need to be tracked down
and considered before we make changes in this area.
I'm not trying to discourage anyone from looking at this and hope I
don't but would rather they have a broader overview so that if we
do change then we have a well planned method rather than trying to
hack each area separately.
Regards,
--
Geoff Wing | gcw@pobox.com | gcw@rxvt.org | gcw@zsh.org
next prev parent reply other threads:[~2001-10-22 3:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-21 15:42 Clint Adams
2001-10-21 17:13 ` Bart Schaefer
2001-10-21 18:21 ` Clint Adams
2001-10-22 0:57 ` Geoff Wing
2001-10-22 1:50 ` Clint Adams
2001-10-22 3:23 ` Geoff Wing [this message]
2001-10-22 11:27 ` Clint Adams
2001-10-22 5:20 ` Borsenkow Andrej
2001-10-22 11:32 ` Clint Adams
2001-10-22 12:02 ` Borsenkow Andrej
2001-10-24 13:57 ` Clint Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011022132306.A5808@primenet.com.au \
--to=gcw@zsh.org \
--cc=clint@zsh.org \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).