From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: UNICODE Private Use Area characters in BUFFER
Date: Sun, 23 Oct 2022 12:12:16 +0200 [thread overview]
Message-ID: <CAN=4vMowyKmrQtQb=QTxiVzQJXRubz-o2T12=6aQBHSpkKwOig@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
Zle cannot display UNICODE Private Use Area characters in BUFFER.
% f() BUFFER=$'\uE0B0'
% zle -N f
% bindkey '^T' f
% <Ctrl-T>
Expected: the last line shows the glyph for U+E0B0 (whichever way the
terminal chooses to render it).
Actual: the last line shows <b0> in reverse video.
I haven't looked at the code but my guess is that zle assumes that
characters from Private Use Area never have a native reasonable
representation, so it attempts to show codepoints. This assumption is
incorrect. I think Private Use Area characters shouldn't be handled
specially. If there is no glyph in the terminal's font for a character, let
the terminal decide how to present that.
Note: Private Use Area characters work fine everywhere else. For example,
in PS1.
Roman.
[-- Attachment #2: Type: text/html, Size: 1021 bytes --]
next reply other threads:[~2022-10-23 10:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 10:12 Roman Perepelitsa [this message]
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
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=4vMowyKmrQtQb=QTxiVzQJXRubz-o2T12=6aQBHSpkKwOig@mail.gmail.com' \
--to=roman.perepelitsa@gmail.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).