Re: No terminal echo after certain commands

[ Available lists | Index of freebsd-bugs | Month of Oct 1998 | Week of 20 Oct 1998 | Raw email | View thread | Wrap long lines | Reply | Tag ]
From
Brett Glass <brett@lariat.org>
Date
20 Oct 1998 18:16:18
Subject
Re: No terminal echo after certain commands
Message-ID
4.1.19981020191142.06b355b0@mail.lariat.org

In reply to

[ Hide this part ]
At 08:57 PM 10/20/98 -0400, Steve Friedrich wrote:

>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.

It's possible that anything programmed badly will hang. However, failure
to return the console to usability after a quick exit is not optional.
Otherwise, it does no good to make a quick exit.

>This is all caused
>by someone who doesn't understand UNIX signals and what they were
>designed for.

Sorry, but you're not only insulting but wrong. I've been using UNIX
since 1977.

>I'd bet he is a current or former DOS or Winblows user
>who developed this bad habit there.

You're arguing ad hominem. Which is especially dangerous when you
have no idea whom you're talking about.

Again, ANY way of interrupting a program shouldn't leave the
console unusable.

--Brett


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message


Elapsed time: 0.115 seconds