Date: Tue, 20 Oct 1998 20:57:26 -0400 From: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com> To: "Brett Glass" <brett@lariat.org>, "Studded" <Studded@gorean.org> Cc: "bugs@FreeBSD.ORG" <bugs@FreeBSD.ORG> Subject: Re: No terminal echo after certain commands Message-ID: <199810210058.UAA30643@laker.net>
next in thread | raw e-mail | index | archive | help
On Tue, 20 Oct 1998 17:02:50 -0700, Studded wrote: >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"! > > We eagerly await your patch. It REALLY shouldn't be fixed. It is important to keep INTR handling to the minimum possible exit code possible. Adding "clean-up" code will add potential that programs will "hang" in this clean up code and INTR will no longer work all the time for that program. This is all caused by someone who doesn't understand UNIX signals and what they were designed for. I'd bet he is a current or former DOS or Winblows user who developed this bad habit there. Microsoft stole the idea but created (once again) a very poor implementation. He needs to learn how to exit an application properly, and that is application dependant. He wants a "standard" and he thinks he's got that in INTR. He doesn't. 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810210058.UAA30643>