From owner-freebsd-current Fri Oct 23 17:13:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26070 for freebsd-current-outgoing; Fri, 23 Oct 1998 17:13:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26065 for ; Fri, 23 Oct 1998 17:13:53 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.6) with ESMTP id UAA94912; Fri, 23 Oct 1998 20:14:08 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199810232221.PAA08852@usr07.primenet.com> Date: Fri, 23 Oct 1998 20:18:16 -0400 To: Terry Lambert , current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Interesting 3.0 bug Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:21 PM +0000 10/23/98, Terry Lambert wrote: > Here is an interesting bug. Take the following: It is a long-standing bug in 'more'. I tripped over it recently, and submitted a patch for it. Someone messaged me that they were testing it some time ago (July?), so I had hoped that it would make it into 3.0 release. On the other hand, it is fixed on my system (and I haven't had the time to keep in sync with current), so I haven't been following its progress all that much... :-) (I was also going to submit a patch so 'more' behaves a bit better when hit with a control-c. maybe I'm doing something wrong, but it seems my stty settings are all screwed up if I happen to attention out of 'more'. This is pretty noticable for me, because I've been using control-c to get out of 'more' on other unix platforms for about ten years now...) --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message