zsh-workers
 help / color / mirror / code / Atom feed
From: Jun T <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: UNICODE Private Use Area characters in BUFFER
Date: Sat, 5 Nov 2022 00:32:33 +0900	[thread overview]
Message-ID: <96C622D4-64D7-4EEB-800F-1A43A82F4973@kba.biglobe.ne.jp> (raw)
In-Reply-To: <CAN=4vMpcfEZcFN3W1sG+29r7giWndzcwagSPMtDRHR1ixrzuyg@mail.gmail.com>

Sorry, this is not related with the Roman's original problem
(so can be ignored if you do not use East Asian Ambiguous Width chars).

> 2022/11/04 20:09, Roman Perepelitsa <roman.perepelitsa@gmail.com> wrote:
> 
> Perhaps zsh should have a similar option? Currently, if the terminal
> option is switched on, prompt will break if it includes private use
> area chars.

It is not a problem of zsh. iTerm2 (and other terminals) uses the option
to control the width of both "East Asian Ambiguous Width" and "User Area"
characters (and maybe other characters with ambiguous width). If your
"User Area" characters are all single width, and if you do not use East
Asian ambig. chars, then you are fine just by unsetting the option
(aside from the problem that Zle can't use them).

If you want to use the East Asian ambig. chars (with CJK fonts) then
you need to set the option on to display them correctly (double width),
but zsh (and probably bash/readline) assume them to be single width
(since wcwidth() returns 1) and can't edit them correctly.

This is a well known problem among Japanese (and Chinese/Korean?)
users. But the problem is in wcwidth (or locale definition), and
I think we need not fix it in zsh.


      reply	other threads:[~2022-11-04 15:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23 10:12 Roman Perepelitsa
2022-10-23 16:29 ` Mikael Magnusson
2022-10-23 16:43   ` Roman Perepelitsa
2022-10-23 17:02     ` Bart Schaefer
2022-10-23 17:29       ` Roman Perepelitsa
2022-10-23 18:30         ` Unicode9 (was Re: UNICODE Private Use Area characters in BUFFER) Bart Schaefer
2022-10-23 19:30           ` Roman Perepelitsa
2022-10-23 21:57           ` Mikael Magnusson
2022-10-23 18:54         ` UNICODE Private Use Area characters in BUFFER Bart Schaefer
2022-10-23 19:26           ` Roman Perepelitsa
2022-11-04  9:55         ` Jun T
2022-10-23 22:42     ` Mikael Magnusson
2022-10-23 23:16       ` Roman Perepelitsa
2022-10-23 23:35         ` Bart Schaefer
2022-10-23 23:46           ` Bart Schaefer
2022-10-24  1:27             ` Mikael Magnusson
2022-10-24  1:43               ` Bart Schaefer
2022-10-24 10:50                 ` Roman Perepelitsa
2022-11-04 10:31                   ` Jun T
2022-11-04 10:33                     ` Roman Perepelitsa
2022-11-04 11:06                       ` Jun T
2022-11-04 11:09                         ` Roman Perepelitsa
2022-11-04 15:32                           ` Jun T [this message]

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=96C622D4-64D7-4EEB-800F-1A43A82F4973@kba.biglobe.ne.jp \
    --to=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@zsh.org \
    /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).