From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: problem with multi-byte character on command line (zsh v 5.8)
Date: Wed, 18 May 2022 22:10:29 +0200 [thread overview]
Message-ID: <CAP+y1xAcojDdGaU2W2oatPaGkWvfzRH+Hgpufuz+zPb+zpYgsw@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7Zifu2401hRAWc41siOmOwSX+s3AxOc0i2VTk-bXHHwbg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
Just tried an ubuntu 18.04 with zsh 5.4.2 (x86_64-ubuntu-linux-gnu)
and I am able to reproduce.
I tried also with gnome-terminal, same result.
I have tried en_US.utf8 and it_IT.utf8, can you share yours?
thanks
Pier Paolo Grassi
Il giorno mer 18 mag 2022 alle ore 21:55 Bart Schaefer <
schaefer@brasslantern.com> ha scritto:
> On Wed, May 18, 2022 at 12:40 PM Pier Paolo Grassi <pierpaolog@gmail.com>
> wrote:
> >
> > I use zsh 5.8 (x86_64-pc-linux-musl)
>
> Ahh. I wonder if this is a side-effect of musl's "special" C locale
> (see workers/50235):
>
> >> Starting with version 1.1.11, musl provides a special C locale where
> bytes
> >> 0x80-0xff are treated as abstract single-byte-character units with no
> actual
> >> character identity (they’re mapped into wchar_t values that occupy the
> >> Unicode surrogates range).
>
> > By the way the problem happens only when the cursor is placed before the
> 4-bytes character.
>
> Still not reproducible on Ubuntu 20.
>
[-- Attachment #2: Type: text/html, Size: 1676 bytes --]
next prev parent reply other threads:[~2022-05-18 20:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 17:30 Pier Paolo Grassi
2022-05-18 18:54 ` Bart Schaefer
2022-05-18 19:40 ` Pier Paolo Grassi
2022-05-18 19:55 ` Bart Schaefer
2022-05-18 20:10 ` Pier Paolo Grassi [this message]
2022-05-18 20:12 ` Pier Paolo Grassi
2022-05-19 4:05 ` Bart Schaefer
2022-05-19 8:59 ` Roman Perepelitsa
2022-05-19 14:01 ` Pier Paolo Grassi
2022-05-19 14:11 ` Roman Perepelitsa
2022-05-19 14:12 ` Pier Paolo Grassi
2022-05-19 14:23 ` Ray Andrews
2022-05-19 14:26 ` Roman Perepelitsa
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=CAP+y1xAcojDdGaU2W2oatPaGkWvfzRH+Hgpufuz+zPb+zpYgsw@mail.gmail.com \
--to=pierpaolog@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@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).