From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Parameter expansion oddity in 3.1.5-pws-20
Date: Mon, 31 May 1999 21:35:00 +0000 [thread overview]
Message-ID: <990531213500.ZM8783@candle.brasslantern.com> (raw)
zagzig% x="$(<config.h)"
zagzig% y=( ${(f)"$(<config.h)"} )
zagzig% echo $#y
423
zagzig% z=( ${(f)"${x}"} )
zagzig% echo $#z
423
So far so good.
zagzig% z=( ${(f)"$x"} )
zagzig% echo $#z
1
zagzig% echo $z
8769
Eh? Where did THAT come from? Oh, 8679 is $$, so that latter is being
parsed as ${(f)$} ... the x is ignored. That was sort of understandable
when you couldn't use quotes there, but with the quotes it's confusing.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
reply other threads:[~1999-05-31 21:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=990531213500.ZM8783@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).