From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Jun T <takimoto-j@kba.biglobe.ne.jp>
Cc: zsh-workers@zsh.org
Subject: Re: UNICODE Private Use Area characters in BUFFER
Date: Fri, 4 Nov 2022 11:33:36 +0100 [thread overview]
Message-ID: <CAN=4vMrO+5PjuTupvUyBkgAYi4o=Tto_1v4ATiuRenPVehmu+w@mail.gmail.com> (raw)
In-Reply-To: <9A1737D9-AE8E-4D9A-84B7-3AB2482C82E0@kba.biglobe.ne.jp>
On Fri, Nov 4, 2022 at 11:32 AM Jun T <takimoto-j@kba.biglobe.ne.jp> wrote:
>
>
> > 2022/10/24 19:50, Roman Perepelitsa <roman.perepelitsa@gmail.com> wrote:
> >
> > There is one thing I didn't mention that is relevant. There is at
> > least one terminal (iTerm2) that has an option to treat Private Use
> > Area characters as wide. This option is off by default.
>
> I can't find this option. Do you mean the option "Ambiguous characters
> are double-width"?
That's the one.
Roman.
next prev parent reply other threads:[~2022-11-04 10:34 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 [this message]
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=4vMrO+5PjuTupvUyBkgAYi4o=Tto_1v4ATiuRenPVehmu+w@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=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).