From: Mikael Magnusson <mikachu@gmail.com>
To: gak@klanderman.net
Cc: Zsh list <zsh-workers@zsh.org>
Subject: Re: 'K' subscript flag with associative array?
Date: Tue, 1 Mar 2011 18:09:20 +0100 [thread overview]
Message-ID: <AANLkTimHftC1y2g9tXdOD=-oPhvhh7n7tADt+jEkx_EJ@mail.gmail.com> (raw)
In-Reply-To: <19821.9197.225140.311873@gargle.gargle.HOWL>
On 1 March 2011 17:50, Greg Klanderman <gak@klanderman.net> wrote:
>
> Hi guys, what am I doing wrong here? Shouldn't this:
>
> zsh% echo ${(k)functions[(K)_*]}
>
> give all function names starting with '_'?
>
> It gives me nothing; the 'R' subscript flag does seem
> to work for matching against the bodies of functions
> and returning the names of those functions.
>
> thanks,
> Greg
>
% echo ${(k)functions[(<tab>
---- subscript flags
I -- all keys matched by subscript as pattern
K -- all values where subscript matched by key as pattern
R -- all values matched by subscript as pattern
e -- interpret * or @ as a single key
i -- any one key matched by subscript as pattern
k -- any one value where subscript matched by key as pattern
r -- any one value matched by subscript as pattern
Ie, you want I, not K. What K/k does is somewhat weird, in that it
interprets the keys of the arrays as patterns and check which of those
match the given subscript. With I/i you don't need to specify ${(k)
either, it defaults to showing the keys, but you can give ${(v) to
instead get the values.
--
Mikael Magnusson
next prev parent reply other threads:[~2011-03-01 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 16:50 Greg Klanderman
2011-03-01 17:09 ` Mikael Magnusson [this message]
2011-03-01 17:20 ` Benjamin R. Haskell
2011-03-01 17:28 ` Mikael Magnusson
2011-03-01 18:08 ` Greg Klanderman
2011-03-01 17:13 ` Benjamin R. Haskell
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='AANLkTimHftC1y2g9tXdOD=-oPhvhh7n7tADt+jEkx_EJ@mail.gmail.com' \
--to=mikachu@gmail.com \
--cc=gak@klanderman.net \
--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).