zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users <zsh-users@sunsite.dk>
Subject: Re: part of an associativz array
Date: Fri, 31 Mar 2006 18:27:13 -0800	[thread overview]
Message-ID: <060331182713.ZM8181@torch.brasslantern.com> (raw)

On Mar 31, 10:35pm, Marc Chantreux wrote:
}
} something like : 
} 
} $user[login,uid]
} 
} any idea ?

    ${(v)user[(I)(login|uid)]}

However, you get them in the indeterminate order in which they appear
in the hash, rather than in the order given in the pattern.  To get
them in predictable order, you need something a lot uglier, like

    ${(e):-\$user\[{login,uid}\]}


             reply	other threads:[~2006-04-01  2:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-01  2:27 Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-31 20:35 Marc Chantreux

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=060331182713.ZM8181@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@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).