From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: indirect assignment to array
Date: Thu, 16 Apr 2020 10:37:55 -0700 [thread overview]
Message-ID: <CAH+w=7ZB5GPi2VD3BiBDukv6UtK1oevjzdQxgH_eVpUAKWFRgw@mail.gmail.com> (raw)
In-Reply-To: <CAP+y1xAjAub4cN_N1mgQUp-kZFpCRRRMzj3Ro6g68P9d1NQJTg@mail.gmail.com>
"Sanitizing" a varname for (P) expansion is context-dependent. For
example, this is "legal":
varname='x[$(echo 3)]'
: ${(AP)varname::=foo}
The point being, there's no straightforward internal test that zsh
could apply to ${(P)varname} that would correctly reject "unsanitary"
references. I suppose we could do something similar to Perl's taint
checks and prevent (P) from being used on environment variables that
have not been (re)assigned since the current shell started up.
next prev parent reply other threads:[~2020-04-16 17:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 23:01 Pier Paolo Grassi
2020-04-15 23:13 ` Mikael Magnusson
2020-04-15 23:42 ` Pier Paolo Grassi
2020-04-15 23:54 ` Bart Schaefer
2020-04-16 0:05 ` Pier Paolo Grassi
2020-04-16 0:12 ` Bart Schaefer
2020-04-16 16:02 ` Pier Paolo Grassi
2020-04-16 16:28 ` Sebastian Gniazdowski
2020-04-16 18:04 ` Pier Paolo Grassi
[not found] ` <CAP+y1xDa=fUvaP=gwbawRmcfwjq0ZH1KEnt=wTX4zOKaT4mzyQ__13411.9792653777$1587060411$gmane$org@mail.gmail.com>
2020-04-16 20:24 ` read -r and bad surprises (Was: indirect assignment to array) Stephane Chazelas
2020-04-16 21:06 ` Pier Paolo Grassi
[not found] ` <CAP+y1xAG3ayQNE3JqeF_YOT5FZ9pLiUAF5TmPVoOv+nPyjK30A__22203.4378488146$1586994256$gmane$org@mail.gmail.com>
2020-04-16 16:30 ` indirect assignment to array Stephane Chazelas
2020-04-16 16:37 ` Pier Paolo Grassi
2020-04-16 17:37 ` Bart Schaefer [this message]
2020-04-16 17:43 ` Pier Paolo Grassi
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='CAH+w=7ZB5GPi2VD3BiBDukv6UtK1oevjzdQxgH_eVpUAKWFRgw@mail.gmail.com' \
--to=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).