zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
	<zsh-workers@sunsite.auc.dk>
Subject: RE: ${_comps[(K)*diff*]}
Date: Fri, 10 Mar 2000 13:57:51 +0300	[thread overview]
Message-ID: <001901bf8a7f$7af9bc90$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <200003101032.LAA03460@beta.informatik.hu-berlin.de>

>
> The keys of $_comps are used as patterns (none of them is a real
> pattern, they are just strings -- the names of commands and special
> context), but none of them matches the string `*diff*'. So you get
> nothing. Of course. Right? Maybe what you wanted is the (I) flag?
> (That (I) and (K) do what they do and that they are named the way they
> are named may be a bit irritating -- probably less when thinking about
> normal arrays instead of associations -- but that has historical
> reasons. (K) just came later.)
>

O.K., sorry, I was confused by manual. The description in (k), (K): "the first value whose
key matches the EXP" means (unless my english completely fails me) STRING key is matched
against PATTERN EXP. The usual usage is "string matches pattern", is not it? I hope,
somebody with native english can clarify it.

And the reference in (k) description "this behaves like `r'" just adds to confusion.

Sorry for the noice (yes, I actually meant (I) in this case)

-andrej


  reply	other threads:[~2000-03-10 10:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-10 10:32 ${_comps[(K)*diff*]} Sven Wischnowsky
2000-03-10 10:57 ` Andrej Borsenkow [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-10  9:54 ${_comps[(K)*diff*]} Sven Wischnowsky
2000-03-10 10:04 ` ${_comps[(K)*diff*]} Andrej Borsenkow
2000-03-09 16:50 ${_comps[(K)*diff*]} Andrej Borsenkow
2000-03-09 18:43 ` ${_comps[(K)*diff*]} Bart Schaefer

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='001901bf8a7f$7af9bc90$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.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).