From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH (?): Re: suspend while loop.
Date: Fri, 19 May 2000 14:49:58 +0000 [thread overview]
Message-ID: <1000519144958.ZM625@candle.brasslantern.com> (raw)
In-Reply-To: <1000519083021.ZM282@candle.brasslantern.com>
On May 19, 8:30am, Bart Schaefer wrote:
} Subject: Re: PATCH (?): Re: suspend while loop.
}
} However, that doesn't affect 3.0.8, so I think I'm going to go ahead with
} 11461 for that release (unless somebody hollers today to stop me).
Here's one other oddment:
zagzig% cat | while read line; do echo $line; done; :
^Z^C
zsh: suspended cat |
zsh: running while read line; do; echo $line; done
zagzig% jobs
[1] + suspended cat |
running while read line; do; echo $line; done
zagzig% fg
[1] + continued cat | while read line; do; echo $line; done
foo
zagzig%
According to Etc/BUGS, the `; :' forces zsh to fork before starting the
while loop. So in that case I would have expected ^Z to work, but it
doesn't. Following the ^Z with a ^C appears to background the job, but
that hasn't really happened either; the while loop is not running, it's
already gotten a failure return from read. Is it sitting there waiting
for "cat" to die? (Which cat does, from a closed stdout, I think, as
soon as you give it any input.)
I'm still not going to try to deal with this for 3.0.8 except to mention
it in BUGS.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-05-19 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-19 7:43 Sven Wischnowsky
2000-05-19 8:30 ` Bart Schaefer
2000-05-19 14:49 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-18 8:37 Sven Wischnowsky
2000-05-18 16:53 ` PATCH (?): " 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=1000519144958.ZM625@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).