From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Hmm, something wrong with _multi_parts?
Date: Mon, 21 Feb 2000 08:52:57 +0000 [thread overview]
Message-ID: <1000221085257.ZM16501@candle.brasslantern.com> (raw)
The doc says:
_multi_parts SEP ARRAY
This function gets two arguments: a separator character and an
array. As usual, the ARRAY may be either the name of an array
parameter or a literal array in the form `(foo bar)' (i.e. a list
of words separated by white space in parentheses). [...]
But if I call it with "a literal array in the form `(foo bar)'" it behaves
very strangely. Stuffing the same strings into an actual array and then
using the name of that array works as I expect.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next reply other threads:[~2000-02-21 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-21 8:52 Bart Schaefer [this message]
2000-02-21 9:14 Sven Wischnowsky
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=1000221085257.ZM16501@candle.brasslantern.com \
--to=schaefer@candle.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).