From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
"Clint Adams" <schizo@debian.org>, <zsh-workers@sunsite.dk>
Cc: "Michal Politowski" <mpol@charybda.icm.edu.pl>,
<101523-forwarded@bugs.debian.org>
Subject: RE: Bug#101523: zsh segmentation fault
Date: Wed, 20 Jun 2001 10:51:11 +0400 [thread overview]
Message-ID: <000201c0f955$63fa7a70$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <1010620040105.ZM1105@candle.brasslantern.com>
>
> I will point out that there's a rather nasty bug in shoop.sh on line 61:
>
> local orgargs="$@"
>
> This will almost certainly not do what is wanted; it'll set orgargs to be
> $1 and will make local variables whose names are the rest of the
> arguments.
> Then later,
>
> set -- $orgargs
>
> will also not produce the desired effect.
>
This is related to export foo=$(cmd) problem we have discussed. Obviously,
other shells treat {export|local|typeset} foo=bar w.r.t. word splitting
exactly the same as foo=bar, i.e. they do not split in assignments here.
Did not we have some patch for it, at least in HEAD? Looks, like it should
be in 4.0.
Have
next prev parent reply other threads:[~2001-06-20 6:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010619225633.A7077@Amber.lab.icm.edu.pl>
2001-06-19 22:33 ` Clint Adams
2001-06-20 4:01 ` Bart Schaefer
2001-06-20 6:51 ` Andrej Borsenkow [this message]
2001-06-20 7:59 ` Andrej Borsenkow
2001-06-20 16:47 ` KSH_TYPESET and 4.0.2 Bart Schaefer
2001-06-20 18:33 ` Peter Stephenson
2001-06-20 16:04 ` Bug#101523: zsh segmentation fault Bart Schaefer
2001-06-20 10:01 ` Peter Stephenson
2001-06-20 10:10 ` Peter Stephenson
2001-06-20 4:57 ` 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='000201c0f955$63fa7a70$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=101523-forwarded@bugs.debian.org \
--cc=mpol@charybda.icm.edu.pl \
--cc=schaefer@candle.brasslantern.com \
--cc=schizo@debian.org \
--cc=zsh-workers@sunsite.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).