From: "Jun. T" <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: (LC_ALL=C; set -x 128 129; printf "%s\n" ${(#)@} | hexdump -C)
Date: Fri, 1 Sep 2023 02:38:21 +0900 [thread overview]
Message-ID: <88812889-04BC-412A-85BE-BDAA2326B29B@kba.biglobe.ne.jp> (raw)
In-Reply-To: <CAH+w=7b58OFubjUOdYuqm0U3hYPKFbX-GSuj7R7H6T8jmtTG2Q@mail.gmail.com>
> 2023/08/31 4:45, Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> Doc for (#) says:
>
> If the MULTIBYTE option is set and the number is greater than 127
> (i.e. not an ASCII character) it is treated as a Unicode
> character.
It seems that this translation succeeds only if UTF-8 locale is in use.
The translation is done in function substevalchar(), but in C locale it
fails to convert and fallbacks to 'no translation':
$ LC_ALL=C zsh -f
% n=128
% printf "%s\n" ${(#)n} | hexdump -C
00000000 80 0a |..|
00000002
substevalchar() calls getkeystring() for the conversion, and
wctomb() (utils.c:6983) fails (returns -1), and zerr() sets
errflag.
If we use an array instead of sclar:
% a=( 128 129 )
% printf "%s\n" ${(#)a} | hexdump -C
00000000 22 0a 22 |"."|
00000003
In this case, errflag is set when translating a[0]=128, but it is
not reset and still set to 1 when substevalchar() is called for a[1].
Then substevalchar() immediately returns NULL (subst.c:1496).
Now paramsubst() sets haserr=1 (subst.c:3592) and returns NULL at
line 3609 (although errflag is reset at line 3606),
and stringsubst() also returns NULL (line 327),
and prefork() quits at line 146 (probably before removing " " from
t"%s\n").
So we need to reset (or save/restore) errflag somewhere...
And, with multibyte option on but with C locale, what is the
correct behavior of ${(#)n} for n > 127 ?
next prev parent reply other threads:[~2023-08-31 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 7:27 Stephane Chazelas
2023-08-30 19:45 ` Bart Schaefer
2023-08-31 17:38 ` Jun. T [this message]
2023-09-07 14:26 ` Jun. T
2023-09-07 16:33 ` Peter Stephenson
2023-09-08 16:30 ` Jun. T
2023-09-11 8:57 ` Peter Stephenson
2023-09-11 12:11 ` Jun. T
2023-09-13 9:59 ` Jun T
2023-09-21 9:26 ` 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=88812889-04BC-412A-85BE-BDAA2326B29B@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).