From: John (Most modern computers would break if you stood on them) Mackin <john@ civil.su.oz.au>
To: Tom Culliton x2278 <culliton@srg.af.mil>, rc@hawkwind.utcs.toronto.edu
Subject: Re: List of known gotchas and patches
Date: Fri, 24 Sep 1993 11:05:01 -0400 [thread overview]
Message-ID: <199309250105.27728.rc.baloj@civil.su.oz.au> (raw)
In-Reply-To: <9309221341.aa26638@ceres.srg.af.mil>
There's one known _bug_ with rc-1.4, and that's in its signal
handling. Byron and I have tossed this back and forth several
times; as far as I know, he hasn't fixed it, and I know I haven't.
(Note that this bug was NOT present in pre-release versions of
1.4; it was in 1.3, I reported it to Byron and he fixed it, and
then he broke it again in the 1.4 release version.)
The bug is that rc doesn't wait correctly for backquoted commands
to complete on signals, so that if you have a backquoted command
running which traps interrupts and you type your interrupt
character, you end up with a mess.
OK,
John.
prev parent reply other threads:[~1993-09-24 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-09-22 17:41 Tom Culliton x2278
1993-09-22 23:59 ` CJS Vance
1993-09-24 15:05 ` John Mackin [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=199309250105.27728.rc.baloj@civil.su.oz.au \
--to=john@civil.su.oz.au \
--cc=culliton@srg.af.mil \
--cc=rc@hawkwind.utcs.toronto.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).