From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Geoff Wing <mason@primenet.com.au>
Cc: zsh-workers@math.gatech.edu
Subject: Re: RC_EXPAND_PARAM bug
Date: Tue, 29 Jul 1997 20:56:29 -0700 [thread overview]
Message-ID: <970729205629.ZM19139@candle.brasslantern.com> (raw)
In-Reply-To: <19970730130411.45672@primenet.com.au>
On Jul 30, 1:04pm, Geoff Wing wrote:
} Subject: Re: RC_EXPAND_PARAM bug
}
} :} ... shouldn't 1${^^x} produce one string "1x y"? And then the
} :} expansion of 1${^a}1${^^x} be the string "1a1x y 1b1x y"? Your logic
} :} indicates to me that it's producing array like thingies. Is this dependant
} :} on some other wierd option? Please explain before I go mental.
} :The trick there is that x is an array variable, so it produces two strings.
}
} Yes, but I still don't get it. ^^ should prevent expansion, shouldn't it.
It prevents rc_expand_param. It doesn't prevent array expansion. That
is, it prevents (x y) from being combined with the rest of the string in
every possible combination; it doesn't make (x y) into a string istead of
into an array. You need quoting for that.
So either 1a1x 1ay 1b1x 1by is right, or else it should be 1a1x 1b1x y.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1997-07-30 4:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-28 13:42 Andrew Main
1997-07-28 16:26 ` Bart Schaefer
1997-07-29 6:04 ` Zoltan Hidvegi
1997-07-29 7:09 ` Bart Schaefer
1997-07-29 7:36 ` Zoltan Hidvegi
1997-07-29 7:47 ` Geoff Wing
1997-07-29 16:27 ` Bart Schaefer
1997-07-30 3:04 ` Geoff Wing
1997-07-30 3:56 ` Bart Schaefer [this message]
1997-07-30 5:16 ` Zoltan Hidvegi
1997-07-30 5:46 ` Andrej Borsenkow
1997-07-30 6:11 ` Bart Schaefer
1997-07-30 6:51 ` Zoltan Hidvegi
1997-07-30 7:33 ` Bart Schaefer
1997-07-30 8:18 ` Andrew Main
1997-07-30 15:54 ` Andrej Borsenkow
1997-07-30 17:05 ` Bart Schaefer
1997-08-01 13:17 ` Andrej Borsenkow
1997-08-01 18:18 ` Bart Schaefer
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=970729205629.ZM19139@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=mason@primenet.com.au \
--cc=zsh-workers@math.gatech.edu \
/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).