From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Zoltan Hidvegi <hzoli@frontiernet.net>
Cc: zsh-workers@math.gatech.edu (Zsh hacking and development)
Subject: Re: RC_EXPAND_PARAM bug
Date: Wed, 30 Jul 1997 00:33:23 -0700 [thread overview]
Message-ID: <970730003323.ZM19948@candle.brasslantern.com> (raw)
In-Reply-To: <199707300651.CAA01564@hzoli.home>
On Jul 30, 2:51am, Zoltan Hidvegi wrote:
} Subject: Re: RC_EXPAND_PARAM bug
}
} If `a' is empty, you want $^a/* expand to nothing, otherwise you would
} get the list of files in the root directory which you do not want.
} Such tricks are used in several zsh scripts I guess, and this is the
} preferable behaviour. And it always worked this way, that's the point
} where there is not difference between versions.
That's fine, then.
} One might require the evaluation of the suffix even if it is discarded
} later. Do you think it is preferable?
I think perhaps it is, especially if the suffix contains arithmetic or
command substitutions that might have side effects.
} > What does the real "rc" shell do?
}
} I do not think this has anything to do with rc.
I'm pretty sure that it does. All the RC_ options are things that "rc"
does, just like the CSH_ options are things CSH_ does, and KSH_, etc.
I believe Paul originally named all the options that were borrowed from
other shells by that convention.
} > } It looks illogical. Either the latter should be 'ax b1x ay b1y' or the
} > } former 'a1x b1x y'.
} >
} > I agree with Andrej on that. If you're going to map over lists, you
} > have to map over them in the prefix too, not just in the suffix.
} >
} > However, I don't like the behavior of (3), i.e. that when ${x} is a list
} > then the word break interrupts the rc-expansion. I'd prefer that the
} > expansion proceed across the suffix in the same way regardless of whether
} > x is an array or a string, and then introduce the word breaks at the end.
}
} I do not understand exatly what you mean, but I'm leaning towards option
} 3.
Consider:
a=(a b)
c="c d"
e=(e f)
${^a}${c}${^e} --> "ac de" "bc de" "ac df" "bc df"
Now:
c=(c d)
Option 2: ${^a}${c}${^e} --> ac de bc de ac df bc df
Option 3: ${^a}${c}${^e} --> ac bc de df
I like the symmetry between (2) and the case where c is a string.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1997-07-30 7:53 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
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 [this message]
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=970730003323.ZM19948@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=hzoli@frontiernet.net \
--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).