From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: unset arbitrary associative array element
Date: Sun, 12 Aug 2018 07:06:57 +0100 [thread overview]
Message-ID: <20180812060657.3ipyrg4xyxjp3b3e@chaz.gmail.com> (raw)
In-Reply-To: <CAKc7PVDNipoD=1FZQXF5qz2wf=nOMP-foabaWVNp+zBWanoK4w@mail.gmail.com>
2018-08-11 16:55:33 +0200, Sebastian Gniazdowski:
> On Sat, 11 Aug 2018 at 13:22, Stephane Chazelas
> <stephane.chazelas@gmail.com> wrote:
> > Is there any other way, other than recreating the full array
> > with something like:
> >
> > hash=("${(@kv)hash[(I)^$key]}") # untested
>
> I once reported some unset-key impossibilities, and Bart and Peter
> added a (b) flag. Maybe it helps here too. Could someone recall what
> this flag does?
[...]
Thanks Sebastian,
unset "hash[${(b)key}]"
does work for keys with "]" or "\" and for characters that
contain bytes 0x5c/5d, but not for the empty key.
Sounds like that problem can be fixed by allowing
unset 'hash[]'
like in ksh93. It would also be useful to allow
hash[]=value
as well (k=; hash[$k]=value and hash+=('' value) do work).
As for the characters with byte 0x5c in their content, that's a
more general problem.
If you want to test, try for instance:
LC_ALL=zh_HK.big5hkscs luit
And within luit:
hash[α]=foo
# and so on
α in BIG5 or BIG5-HKSCS is encoded as 0xa3 0x5c, 0x5c also being
the encoding of \. ${(b)key} for key='α' expands to α\ (0xa3
0x5c 0x5c).
That trailing 0x5c in the encoding of α is taken as a backslash
in many contexts in zsh.
Beside BIG5 and BIG5-HKSCS, GBK and GB18030 charsets also have
characters that contain 0x5c.
It may not be worth fixing if Chinese/Thai people have all
switched to UTF-8 by now.
--
Stephane
prev parent reply other threads:[~2018-08-12 6:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-11 11:22 Stephane Chazelas
2018-08-11 14:55 ` Sebastian Gniazdowski
2018-08-12 3:38 ` Sebastian Gniazdowski
2018-08-12 6:06 ` Stephane Chazelas [this message]
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=20180812060657.3ipyrg4xyxjp3b3e@chaz.gmail.com \
--to=stephane.chazelas@gmail.com \
--cc=sgniazdowski@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).