From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-users@sunsite.auc.dk
Subject: Re: [3.1.9 bug] zsh does not die
Date: Wed, 8 Nov 2000 11:40:17 +0100 (MET) [thread overview]
Message-ID: <200011081040.LAA21356@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Vincent Lefevre's message of Tue, 7 Nov 2000 11:15:14 +0100
Vincent Lefevre wrote:
> With zsh 3.1.9 under OSF1, I execute a telnet and delete the window.
> If the window was an xterm, no problem, zsh is properly killed. But
> if it was an rxvt (version 2.18), zsh does not die and takes a lot
> of CPU time.
That sounds like that old bug we fixed for xterm.
But I can't reproduce it here, with the latest zsh and rxvt v2.75 on
OSF1 (DU V4.0f).
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-11-08 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 10:40 Sven Wischnowsky [this message]
2000-11-08 18:32 ` Vincent Lefevre
-- strict thread matches above, loose matches on Subject: below --
2000-11-07 10:15 Vincent Lefevre
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=200011081040.LAA21356@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-users@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).