Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Oct 1998 20:02:41 -0600
From:      Brett Glass <brett@lariat.org>
To:        Matthias Buelow <mkb@altair.mayn.de>
Cc:        bugs@FreeBSD.ORG
Subject:   Re: No terminal echo after certain commands 
Message-ID:  <4.1.19981020195137.00c54280@mail.lariat.org>
In-Reply-To: <199810210149.DAA01224@altair.mayn.de>
References:  <Your message of "Tue, 20 Oct 1998 19:15:26 MDT."             <4.1.19981020191142.06b355b0@mail.lariat.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.1.19981020195137.00c54280>