From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] death on keypress
Date: Fri, 07 Dec 2007 10:13:20 -0800 [thread overview]
Message-ID: <1197051153-sup-996@south> (raw)
In-Reply-To: <20071207031758.GF29074@danconia.atlantis.saintaardvarkthecarpeted.com>
Excerpts from Saint Aardvark the Carpeted's message of Thu Dec 06 19:17:58 -0800 2007:
> Ian Taylor disturbed my sleep to write:
> > Should ctrl-\ cause sup to crash for any particular reason?
>
> In Bash, at least, this sends SIGQUIT (I believe) to the process in
> the foreground; this tells it to quit and dump core.
Yep, this is not a Sup issue. Try it with top and any other curses
programs you have---they all abort.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2007-12-07 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 2:51 Ian Taylor
2007-12-07 3:17 ` Saint Aardvark the Carpeted
2007-12-07 18:13 ` William Morgan [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=1197051153-sup-996@south \
--to=wmorgan-sup@masanjin.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox