From: "Johann 'Myrkraverk' Oskarsson" <johann@myrkraverk.com>
To: ZSH Users <zsh-users@sunsite.dk>
Subject: Re: Keying arrays to names: is there an array of arrays?
Date: Sun, 28 May 2006 21:32:40 +0000 [thread overview]
Message-ID: <m3wtc5esxz.fsf@jin.myrkraverk.com> (raw)
In-Reply-To: <060528111724.ZM29224@torch.brasslantern.com> (Bart Schaefer's message of "Sun, 28 May 2006 11:17:24 -0700")
Bart Schaefer <schaefer@brasslantern.com> writes:
> That's actually incorrect. The (z) option is already splitting the
> value; you shouldn't need or want to split it again with (s: :). If
> the setting of IFS is preventing (z) from working properly, that's
> probably a bug, but in any case the workaround is to make IFS local.
Well, all *I* know is that the s: : is needed -- at least without the
local IFS solution. If someone can (and is willing) to convince me
that's a bug (I don't yet understand all the flags involved in these
expansions) I can cook up some nice test case/bug report.
Thank you for the local IFS, that does look/appear to be cleaner.
> If you're going to use these functions for hash access anyway, then
> you might as well also use ${(q)2} instead of $2 in both of them, to
> avoid issues with non-alphanumeric keys.
Thank you. I'll keep that in mind if I run into the problem (dunno,
if I will, I'm prototyping an app and the keys will be filenames).
Johann
--
johann myrkraverk com (you know the drill with the @ and .)
I classify Outlook mail as spam, please use something else for
private messages.
prev parent reply other threads:[~2006-05-28 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 14:20 Johann 'Myrkraverk' Oskarsson
2006-05-26 15:26 ` Marc Chantreux
2006-05-26 15:40 ` Peter Stephenson
2006-05-26 15:58 ` Peter Stephenson
2006-05-27 19:09 ` Johann 'Myrkraverk' Oskarsson
2006-05-27 22:10 ` Bart Schaefer
2006-05-28 2:34 ` Johann 'Myrkraverk' Oskarsson
2006-05-28 18:17 ` Bart Schaefer
2006-05-28 21:32 ` Johann 'Myrkraverk' Oskarsson [this message]
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=m3wtc5esxz.fsf@jin.myrkraverk.com \
--to=johann@myrkraverk.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).