From: "Bart Schaefer" <schaefer@brasslantern.com>
To: <zsh-workers@sunsite.auc.dk>
Subject: Re: BUG: zsh-3.1.5-pws-14: parameter expansion not working properly
Date: Fri, 16 Apr 1999 02:04:18 -0700 [thread overview]
Message-ID: <990416020418.ZM13627@candle.brasslantern.com> (raw)
In-Reply-To: <000d01be87dd$961a9800$21c9ca95@mowp.siemens.ru>
On Apr 16, 11:48am, Andrej Borsenkow wrote:
} Subject: RE: BUG: zsh-3.1.5-pws-14: parameter expansion not working proper
}
} It is *impossible* to split array elements. It is no joke. Arrays are joined
} together before splitting - so, the result I get is much much different.
}
} Subsequent splitting on IFS does not help, as it can change "too much"
}
} May be, nobody really needs it (I missed it time to time). And may be, there
} is always workaround. But it is really really weird ...
The obvious workaround is to explicitly join and then split:
zsh% foo=(a:b x:y)
zsh% print -l ${(j/:/s/:/)foo}
a
b
x
y
One might however argue that this looks odd:
zsh% print -l ${(s/:/j/:/)foo}
a
b
x
y
The flags are always applied in an internally-defined order, not in the
order they appear in the flag list. But flag list ordering does matter
if you happen to repeat a flag:
zsh% print -l ${(s/:/s/ /)foo}
a:b
x:y
All that aside, a desirable (?) effect of the current interpretation is
that join reverses split (except for the initial array-to-scalar change):
zsh% print -l ${(j/:/)${(s/:/)foo}}
a:b x:y
With your interpretation, this would yield a:b:x:y. Of course, since
split can't logically reverse join, maybe it's not necessary that join
be capable of reversing split.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-04-16 9:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-16 7:36 Sven Wischnowsky
1999-04-16 7:48 ` Andrej Borsenkow
1999-04-16 9:04 ` Bart Schaefer [this message]
1999-04-16 9:26 ` Andrej Borsenkow
1999-04-18 23:39 ` Bart Schaefer
1999-05-07 11:51 ` Peter Stephenson
1999-05-07 13:36 ` Sven Wischnowsky
1999-05-09 17:49 ` Bart Schaefer
1999-05-10 8:28 ` PATCH: mult_isarr documentation Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
1999-05-10 9:13 BUG: zsh-3.1.5-pws-14: parameter expansion not working properly Sven Wischnowsky
1999-04-15 12:08 Sven Wischnowsky
1999-04-15 20:10 ` Bart Schaefer
1999-04-15 6:49 Sven Wischnowsky
1999-04-15 11:03 ` Bart Schaefer
1999-04-12 7:17 Sven Wischnowsky
1999-04-14 17:27 ` Bart Schaefer
1999-04-10 11:28 Geoff Wing
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=990416020418.ZM13627@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).