From: Tim Goodwin <tjg@star.le.ac.uk>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: Bug#62339: rc bug
Date: Wed, 19 Apr 2000 10:39:44 -0400 [thread overview]
Message-ID: <ZEMAAEbF/TiL9QoA@ltsun0.star.le.ac.uk> (raw)
In-Reply-To: <200004180630.XAA05903@peanut.rakitzis.com>
A big "thank you!" to Byron and Decklin for getting to the bottom of
this bug. I've incorporated their fix, plus a couple of other recent
fixes into a new snapshot, which you can get from here.
http://www.star.le.ac.uk/~tjg/rc/snap/rc-1.6s20000419.tar.gz
This has only been very lightly tested; there might well be some
booboos. After the Easter break, I'll scrutinize the changes again, and
wrap them into a new beta release.
Changes since the last beta are summarized below.
Tim.
2000-04-19
Bug: isatty() tests in input.c are relevant to any fd, not just 0.
Now `. -i /dev/tty' works right.
Bug: fn sigexit wasn't always cleared in child shells.
Bug: `~ () '*'' dumped core.
next prev parent reply other threads:[~2000-04-19 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-18 6:30 Byron Rakitzis
2000-04-19 14:39 ` Tim Goodwin [this message]
[not found] <Pine.LNX.3.96.1000425010821.264C-100000@dwarf>
[not found] ` <QDwAALDY+jgTYAcA@ltsun0.star.le.ac.uk>
2000-04-17 19:59 ` Decklin Foster
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=ZEMAAEbF/TiL9QoA@ltsun0.star.le.ac.uk \
--to=tjg@star.le.ac.uk \
--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).