From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: pws@ifh.de (Peter Stephenson)
Cc: zsh-workers@math.gatech.edu
Subject: Re: Runaway Shell (bug>)
Date: Fri, 21 Jun 1996 14:17:18 +0200 (MET DST) [thread overview]
Message-ID: <199606211217.OAA01462@bolyai.cs.elte.hu> (raw)
In-Reply-To: <199606210900.LAA17786@hydra.ifh.de> from Peter Stephenson at "Jun 21, 96 11:00:30 am"
> Nasty. With NO_BAD_PATTERN, exec.c around line 1177 is repeatedly
> globbing the same line because it is always returned containing
> tokens. Any problem with the having NOBADPATTERN untokenize at that
> point? As globbing is the last operation, I can't see any.
You are right. glob should not leave any tokens there. That was not true
before beta19 and I missed that case.
Zoltan
prev parent reply other threads:[~1996-06-21 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-20 14:41 gene
1996-06-21 9:00 ` Peter Stephenson
1996-06-21 12:17 ` Zoltan Hidvegi [this message]
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=199606211217.OAA01462@bolyai.cs.elte.hu \
--to=hzoli@cs.elte.hu \
--cc=pws@ifh.de \
--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).