From: Alexandre Duret-Lutz <duret_g@epita.fr>
To: zsh-workers@math.gatech.edu
Cc: Jukka Laurila <jplauril@cc.hut.fi>
Subject: Re: Zsh 3.1.6 - ${~foo} expansion bug
Date: 08 Feb 2000 00:16:43 +0100 [thread overview]
Message-ID: <mvbya8wppr8.fsf@phobos.lrde.epita.fr> (raw)
In-Reply-To: Jukka Laurila's message of "Tue, 8 Feb 2000 00:29:23 +0200 (EET)"
>>> "Jukka" == Jukka Laurila <jplauril@cc.hut.fi> writes:
[...]
Jukka> I just tried compiling zsh-3.1.6-dev-17 both with gcc 2.95.2 in my
Jukka> Debian Potato environment and with egcs-2.91.66 in my RedHat 6.1
Jukka> environment (using chroot). The one compiled in Potato was broken
Jukka> but the one compiled in RH 6.1 worked!
Jukka> Could someone try compiling zsh with gcc 2.95.2 and tell me if it
Jukka> breaks?
I can reproduce this with zsh patched up to date (Debian, gcc 2.95.2).
>From my experiments I am tempted to deduce that this is
reproducible as long as you don't call a builtin before
the for loop.
~/tmp/tmp % zsh -f 0:10 #27
phobos% f=*
phobos% for i ($~f) echo $i
a b c d
phobos% for i ($~f) echo $i
a
b
c
d
phobos%
~/tmp/tmp % zsh -f 0:10 #27
phobos% gcc
gcc: No input files
phobos% f=*
phobos% for i ($~f) echo $i
a b c d
phobos%
~/tmp/tmp % zsh -f 0:10 #27
phobos% cd .
phobos% f=*
phobos% for i ($~f) echo $i
a
b
c
d
phobos%
~/tmp/tmp % zsh -f 0:11 #27
phobos% /bin/echo
phobos% f=*
phobos% for i ($~f) echo $i
a b c d
phobos%
--
Alexandre Duret-Lutz
next prev parent reply other threads:[~2000-02-07 23:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-07 20:49 Jukka Laurila
2000-02-07 21:40 ` Bart Schaefer
2000-02-07 22:29 ` Jukka Laurila
2000-02-07 23:16 ` Alexandre Duret-Lutz [this message]
2000-02-08 5:19 ` Bart Schaefer
2000-02-07 23:25 ` Thomas Köhler
2000-02-08 9:25 Sven Wischnowsky
2000-02-11 19:27 ` Peter Stephenson
2000-02-14 9:13 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=mvbya8wppr8.fsf@phobos.lrde.epita.fr \
--to=duret_g@epita.fr \
--cc=jplauril@cc.hut.fi \
--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).