From owner-freebsd-bugs Tue Oct 20 17:22:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21515 for freebsd-bugs-outgoing; Tue, 20 Oct 1998 17:22:30 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21501 for ; Tue, 20 Oct 1998 17:22:28 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id SAA08360; Tue, 20 Oct 1998 18:21:55 -0600 (MDT) Message-Id: <4.1.19981020181535.06ad01a0@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 20 Oct 1998 18:16:22 -0600 To: "Steve Friedrich" , "Studded" From: Brett Glass Subject: Re: No terminal echo after certain commands Cc: "bugs@FreeBSD.ORG" In-Reply-To: <199810202258.SAA25216@laker.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, if you really had an emergency, you'd CERTAINLY want your terminal to work! I do not think that anyone would consider this optional. --Brett At 06:57 PM 10/20/98 -0400, Steve Friedrich wrote: >On Tue, 20 Oct 1998 15:53:13 -0600, Brett Glass wrote: > >>No program should leave the console partially or completely disabled, >>no matter how it exits. Sounds like this is a bug in "more"! > >Actually, Control-C is used by a user who specifically wants to exit >RIGHT NOW (emergency exit) with a very short path thru any code that >could hang. It is NOT meant as a non-emergency exit signal. > >In short, Studded is right, you are not. >Unix systems measure "uptime" in years, Winblows measures it in minutes. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message