From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Oliver Kiddle <opk@u.genie.co.uk>, zsh-workers@sunsite.dk
Subject: Re: PATCH: completion for subscript flags
Date: Fri, 4 May 2001 17:28:23 -0700 [thread overview]
Message-ID: <010504172823.ZM19667@candle.brasslantern.com> (raw)
In-Reply-To: <3AF333EC.7066178F@u.genie.co.uk>
On May 4, 11:57pm, Oliver Kiddle wrote:
> Subject: PATCH: completion for subscript flags
>
> This adds completion for subscript flags in _subscript so as to further
> reduce the number of times I have to reach for the manual.
Very nice.
> One problem is that _values is not powerful enough to handle the
> arguments such as you have with the s flag (e.g. in $PATH[(s.:.)4]).
> Any ideas on how to handle this or is it not worth bothering?
Hmm. Something like (this is just meant as example code, not something
that would drop in anywhere):
[[ $flags = (#b)([snb])(?)(*) ]] && {
local f=$match[1] d=$match[2] r=$match[3]
[[ $r = (#b)([^$d]##)$d* ]]
}
> I'd appreciate if someone could check through my descriptions,
> particularly those for associative arrays. I have a suspicion that some
> of the flags aren't working actually but I may just be confused.
I think you've got some of the descriptions wrong. The wording gets
tricky here.
> + case ${(Pt)${compstate[parameter]}} in
> + assoc*) flags=(
> + '(R k K i I)r[return first matching value]'
> + '(r k K i I)R[return value of first matching key]'
'(R k K i I)r[return first value matched by subscript]'
'(r k K i I)R[return all values matched by subscript]'
> + '(r R K i I)k[return all values with matching keys]'
> + '(r R k i I)K[return value of first matching key]'
'(r R K i I)k[return first value where subscript matched by key]'
'(r R k i I)K[return all values where subscript matched by key]'
> + '(r R k K I)i[return first matching key]'
> + '(r R k K i)I[return all matching keys]'
These are correct, but I'd reword as:
'(r R k K I)i[return first key matched by subscript]'
'(r R k K i)I[return all keys matched by subscript]'
The difference is that r and R compare as [[ value = subscript ]] whereas
k and K do [[ subscript = key ]] and i and I do [[ key = subscript ]] --
do you see the analogy to which thing is treated as a pattern?
> + array*) flags=($flags
> + 'n[specify match to return]'
> + 'b[begin with specified element]'
> + '(r R k K i)I[reverse subscript giving index of last match]'
> + '(r k K i I)R[reverse subscripting giving last match]'
> + '(R k K i I)r[reverse subscripting giving first match]'
You seem to have forgotten
'(r R k K I)i[reverse subscript giving index of first match]'
next prev parent reply other threads:[~2001-05-05 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 22:57 Oliver Kiddle
2001-05-05 0:28 ` Bart Schaefer [this message]
2001-05-05 17:26 ` Bart Schaefer
2001-05-06 4:59 ` Andrej Borsenkow
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=010504172823.ZM19667@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=opk@u.genie.co.uk \
--cc=zsh-workers@sunsite.dk \
/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).