From: culliton@srg.af.mil (Tom Culliton x2278)
To: rc@archone.tamu.edu
Subject: rc and readline and SIGINT
Date: Fri, 17 Apr 1992 16:52:51 -0500 [thread overview]
Message-ID: <9204171752.aa00070@ceres.srg.af.mil> (raw)
Well, I'm going to throw this one open to everyone and maybe someone like
Chet will read it and come up with a good answer.
Under rc-1.2 with or without readline if I hit the key for SIGINT it
aborted the current input line. This was good and righteous and all that.
Under rc-1.3 with readline it no longer seemed to work right. Since
1.3 had signal handling (and other) problems it was hard to be sure
what the trouble was.
Under rc-1.4beta without readline SIGINT works as expected/desired and
aborts the line. With readline the line doesn't get executed, but it
doesn't get cleared or quit either and further input is accepted but
not executed. Furthermore if signal handling in readline is disabled
the key loses it's meaning as SIGINT! (This is strictly readlines
"fault")
While I can live with this, it is rather unaesthetic and just plain
bugs me. Any clues?
Tom
next reply other threads:[~1992-04-17 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-04-17 21:52 Tom Culliton x2278 [this message]
1992-04-21 18:36 Chet Ramey
1992-04-24 21:46 Tom Culliton x2278
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=9204171752.aa00070@ceres.srg.af.mil \
--to=culliton@srg.af.mil \
--cc=rc@archone.tamu.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;
as well as URLs for NNTP newsgroup(s).