From: kevinr@mit.edu (Kevin Riggle)
Subject: [sup-talk] Crash report: C-\ in inbox-mode raises an exception
Date: Wed, 30 Apr 2008 07:41:06 -0400 [thread overview]
Message-ID: <1209555404-sup-3139@black-opal> (raw)
I accidentally hit <control>-\ in inbox-mode in Sup, immediately after
opening the application, which caused it to crash.
~/.sup/exception-log.txt contains:
--- SignalException from thread: main
SIGQUIT
./lib/sup/buffer.rb:31:in `select'
./lib/sup/buffer.rb:31:in `nonblocking_getch'
bin/sup:227
FYI.
- Kevin
--
Kevin Riggle (kevinr at mit.edu)
http://free-dissociation.com
next reply other threads:[~2008-04-30 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 11:41 Kevin Riggle [this message]
2008-05-01 21:24 ` William Morgan
2008-05-02 5:00 ` Kevin Riggle
2008-05-02 14:01 ` Marc Hartstein
2008-05-02 14:14 ` Marcus Williams
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=1209555404-sup-3139@black-opal \
--to=kevinr@mit.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox