Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!ginosko!uunet!ateng!chip
From: chip@ateng.com (Chip Salzenberg)
Newsgroups: comp.unix.wizards
Subject: Re: TTY, speak now, or forever
Message-ID: <254CF89E.22674@ateng.com>
Date: 31 Oct 89 01:42:53 GMT
References: <216100015@s.cs.uiuc.edu> <1989Oct24.011505.20515@NCoast.ORG> <254641C0.4960@ateng.com> <3546@scolex.sco.COM>
Organization: A T Engineering, Tampa, FL
Lines: 22

According to natei@sco.COM (Nathaniel Ingersoll):
>In article <254641C0.4960@ateng.com> chip@ateng.com (Chip Salzenberg) writes:
>>And make all control characters optional.  As in, "stty intr none".
>
>Try setting the control character to -1 to undefine it;
>in system V use
>	% stty intr ^-
>
>as per the stty(1) man page.

The stty(1) man page lies.

The command "stty intr '^-'" doesn't make the interrupt character undefined,
it makes it 0xFF.  If I have a terminal that generates 0xFF, or if line
noise is interpreted as 0xFF, then I get a SIGINT.

I renew my request.  I want an "stty intr none" that _works_.
-- 
You may redistribute this article only to those who may freely do likewise.
Chip Salzenberg at A T Engineering;  <chip@ateng.com> or <uunet!ateng!chip>
"'Why do we post to Usenet?'  Naturally, the answer is, 'To get a response.'"
                        -- Brad "Flame Me" Templeton