[17841] in Athena Bugs
Re: sun4 8.3.27: discuss
daemon@ATHENA.MIT.EDU (Brad Thompson)
Mon May 15 12:05:25 2000
Message-Id: <200005151605.MAA03384@manatee.mit.edu>
To: Kev <klmitch@MIT.EDU>
cc: bugs@MIT.EDU
In-Reply-To: Your message of "Mon, 15 May 2000 10:13:44 EDT."
<200005151413.KAA01008@mint-square.mit.edu>
Date: Mon, 15 May 2000 12:05:19 -0400
From: Brad Thompson <yak@MIT.EDU>
> I have seen this behavior in connection with long messages only, with
> less... it may happen with more, but I haven't checked that. What
> seems to be happening is that less is executed with the file on stdin;
> if you do not page to the end of the file before hitting 'q', less
> returns non-zero, and discuss assumes that there was a failure in
> reading the message. Curiously, you can then type 'next' again, and it
> will retrieve the next message in the meeting, of course setting your
> last read transaction to the correct thing.
Camilla pointed this out to me. Under NetBSD, where "more" is "less",
this behavior does not occur. Under Solaris, where "more" is "more",
this behavior does occur. Curiously, more's exit status on Solaris
does not appear to change if you abort a read early (at least when
launched from bash), so I have no idea how more is communicating to
discuss that it "failed".
yak
