From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Mikael Magnusson <mikachu@gmail.com>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: UNICODE Private Use Area characters in BUFFER
Date: Sun, 23 Oct 2022 21:26:51 +0200 [thread overview]
Message-ID: <CAN=4vMoqJyX38SaEsN30rOqxW9vxepy0qNy6QOQjMYNoEc-Pcw@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7YKCV7yftsod+e5J761x_ZyVp9m2CYPcUnK5X8Q9ZO=zw@mail.gmail.com>
On Sun, Oct 23, 2022 at 8:54 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Sun, Oct 23, 2022 at 10:29 AM Roman Perepelitsa
> <roman.perepelitsa@gmail.com> wrote:
> >
> > You are right, iswprint(0xE0B0) returns 0.
>
> Interestingly, ${(V)...} et al. don't consult iswprint(), they just
> call wcs_nicechar_sel() which only consults WCWIDTH().
As far as I can tell, WCWIDTH() always gives the right answer when
building with --enable-unicode9. It's only WC_ISPRINT() that sometimes
gives an incorrect (in my opinion) answer.
> Some characters like $'\u21A9' report and occupy a width of 1, but
> part of the character overlaps the cell to the right when displayed.
This is a property of your font and not of the character. Glyphs don't
have to be confined within their bearings. In monospace fonts they
usually are but even this rule is often broken. The font I'm using
(and the one I recommend to powerlevel10k users) has glyphs that
overlap left, right, top and bottom neighbours.
Roman.
next prev parent reply other threads:[~2022-10-23 19:27 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 [this message]
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
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='CAN=4vMoqJyX38SaEsN30rOqxW9vxepy0qNy6QOQjMYNoEc-Pcw@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=mikachu@gmail.com \
--cc=schaefer@brasslantern.com \
--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).