From owner-freebsd-bugs Tue Oct 20 19:03:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02250 for freebsd-bugs-outgoing; Tue, 20 Oct 1998 19:03:24 -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 TAA02243 for ; Tue, 20 Oct 1998 19:03:22 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id UAA09241; Tue, 20 Oct 1998 20:02:47 -0600 (MDT) Message-Id: <4.1.19981020195137.00c54280@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 20 Oct 1998 20:02:41 -0600 To: Matthias Buelow From: Brett Glass Subject: Re: No terminal echo after certain commands Cc: bugs@FreeBSD.ORG In-Reply-To: <199810210149.DAA01224@altair.mayn.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 03:49 AM 10/21/98 +0200, Matthias Buelow wrote: >It most probably isn't unusable; ^Jreset^J should return it to a >sane state. I've been using "tset", but "reset" does also work. >If you kill -9 a program, there's no way for it to >reset the terminal to the previous state either. True. >I think it's a >little exaggerated for a small utility like "more" to catch all >catchable signals (including SEGV, BUS etc.) just to reset the tty >to its previous state. No, but SIGINT is much more likely to happen, and in fact is the OFFICIAL way to get out of lots of screen-oriented programs. >INTR is in no way different from SEGV or BUS; the user usually >wants the thing to quit fast. True. But so fast that the console is unusable? I'd save that for a signal with greater severity. The usual convention is that ^C makes a quick but still graceful exit, while kill -9 is the take-no-prisoners, don't-clean-up version. /bin/mail is a good example of the use of ^C. Yes, ^C kills the message you're writing, but it doesn't mess up your mail file or your terminal. (In fact, because the ^C can destroy a lot of work, there's an option -- often enabled by default -- to give the user a second chance before quitting.) >If you kill full-screen programs, you have to reset the tty >yourself. Again, it seems to me that if you killed them with a sledgehammer, that would be fine. But ^C? Again, it (or something like it) is the standard way out of too many things. It should clean up, as it does on Slowlaris and other UNIX implementations. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message