From: Huy Le <huyle@ugcs.caltech.edu>
To: zsh-workers@math.gatech.edu
Subject: zsh 2.6-beta13 bug report
Date: Wed, 21 Feb 1996 01:26:46 -0800 [thread overview]
Message-ID: <199602210927.BAA17965@envy.ugcs.caltech.edu> (raw)
zsh v. 2.6-beta13 on HP-UX A.09.01
zsh v. 2.6-beta13 on SunOS 5.4
When I do:
while echo crap >/dev/null; do done
and <CTRL>-C break out of it, most of the time (intermittent) my output
seems to stay redirected, and I have to fix it with
exec >&2
(Note: a difference between HP-UX and Solaris is that, on HP-UX,
I still manage to see my prompt, while on Solaris nothing but
error comes out)
- Huy
next reply other threads:[~1996-02-21 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-21 9:26 Huy Le [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-03-03 20:43 Huy Le
1996-02-23 7:13 Huy Le
1996-02-19 22:06 Huy Le
1996-02-20 0:04 ` Zefram
1996-02-17 21:52 Huy Le
1996-02-18 18:02 ` Zefram
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=199602210927.BAA17965@envy.ugcs.caltech.edu \
--to=huyle@ugcs.caltech.edu \
--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).