From: culliton@srg.af.mil (Tom Culliton x2278)
To: culliton@uunet.UU.NET, rc@hawkwind.utcs.toronto.edu,
schwartz@groucho.cse.psu.edu
Subject: Re: signals and stuff
Date: Tue, 10 May 1994 15:53:29 -0400 [thread overview]
Message-ID: <9405101553.aa27072@ceres.srg.af.mil> (raw)
Well that patch is an improvement, but it's not perfect yet. Testing on
my friendly neighborhood Sparc-station with:
fn sigwinch {eval `/usr/bin/X11/resize; stty sane; echo}
The next command entered after the signal handler is executed complains
about a "parse error". It also fails to clear errno the next time
through rc_readline so that ^D doesn't work unless another command is
executed first. 8-P Blech! (This doesn't happen under SCO Unix...)
next reply other threads:[~1994-05-10 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-05-10 19:53 Tom Culliton x2278 [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-05-10 17:58 Tom Culliton x2278
1994-05-06 22:09 Scott Schwartz
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=9405101553.aa27072@ceres.srg.af.mil \
--to=culliton@srg.af.mil \
--cc=culliton@uunet.UU.NET \
--cc=rc@hawkwind.utcs.toronto.edu \
--cc=schwartz@groucho.cse.psu.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).