From: marc.hartstein@alum.vassar.edu (Marc Hartstein)
Subject: [sup-talk] Crash report: C-\ in inbox-mode raises an exception
Date: Fri, 02 May 2008 10:01:41 -0400 [thread overview]
Message-ID: <1209736414-sup-1744@cabinet> (raw)
In-Reply-To: <1209676957-sup-6855@south>
Excerpts from William Morgan's message of Thu May 01 17:24:17 -0400 2008:
> Reformatted excerpts from Kevin Riggle's message of 2008-04-30:
> > I accidentally hit <control>-\ in inbox-mode in Sup, immediately after
> > opening the application, which caused it to crash.
>
> That's a standard UNIX keybinding like ^C. I could trap it, but I think
> you'll find most other curses programs die if you press it.
It might be nice to provide a "paranoid-quit" option which, like Mutt,
prompts for "are you sure, or did you just hit the wrong key?", and, if
on, bind that routine to all of 'q', SIGINT, and SIGQUIT.
(I keep wanting ^C to interrupt a long-running process within sup like a
!!, and being surprised when it quits and I'm reminded I need to ^G.
And q is way too dangerously easy to hit for someone who migrated over
from Mutt. I'd definitely turn that on, at least for a few months until
the proper keybindings stick in my mind.)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080502/50d1d458/attachment.bin>
next prev parent reply other threads:[~2008-05-02 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 11:41 Kevin Riggle
2008-05-01 21:24 ` William Morgan
2008-05-02 5:00 ` Kevin Riggle
2008-05-02 14:01 ` Marc Hartstein [this message]
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=1209736414-sup-1744@cabinet \
--to=marc.hartstein@alum.vassar.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