From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Bug in mult_isarr
Date: Mon, 10 May 1999 15:58:34 +0200 (MET DST) [thread overview]
Message-ID: <199905101358.PAA15395@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Mon, 10 May 1999 13:21:20 +0200
Peter Stephenson wrote:
> Modifiers and split process substitutions don't seem to go together too
> well with the mult_isarr patch (6046).
>
> % print "${(@)${(@)=$(echo yan tan tethera dick)}:##t*}"
>
> before:
>
> yan dick
>
> after:
>
> yan tan tethera dick
>
> The example that I originally found was presumably triggering the same
> thing,
>
> % print "${(@)${(@f)$(typeset)}:#*local *\=*}"
>
> where you get nothing after the patch. However, I also noticed that in
> that case if you miss out the `:' the shell hangs.
The patch below fixes this -- remember me saying that I had to put the
`mult_isarr = isarr' further up than I would have done if the singleton-
array-to-string conversion hadn't been there?
The second example now works for me, too. I couldn't get it to hang,
though. However, in the shell I tested it I have the magic hashes from
6198 where a simple `typeset' could cause the shell to SEGV -- if you
have that in the shell you tried this with, too, you'll better remove
it -- I hope to send a patch for a module with those special
parameters this week anyway.
Bye
Sven
--- os/subst.c Fri May 7 14:55:12 1999
+++ Src/subst.c Mon May 10 15:46:53 1999
@@ -1465,6 +1465,7 @@
val = aval[0];
else
isarr = 2;
+ mult_isarr = isarr;
}
}
if (casmod) {
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-05-10 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-10 13:58 Sven Wischnowsky [this message]
1999-05-10 16:11 ` Peter Stephenson
-- strict thread matches above, loose matches on Subject: below --
1999-05-10 11:21 Peter Stephenson
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=199905101358.PAA15395@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).