Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbatt!ihnp4!ptsfa!styx!mordor!lll-lcc!pyramid!prls!mips!dce
From: dce@mips.UUCP
Newsgroups: comp.unix.wizards
Subject: Re:  Help! I need an interrupt!! (or something)
Message-ID: <366@quacky.UUCP>
Date: Tue, 5-May-87 10:10:51 EDT
Article-I.D.: quacky.366
Posted: Tue May  5 10:10:51 1987
Date-Received: Thu, 7-May-87 01:32:52 EDT
References: <7236@brl-adm.ARPA>
Reply-To: dce@quacky.UUCP (David Elliott)
Organization: MIPS Computer Systems, Sunnyvale, CA
Lines: 23

In article <7236@brl-adm.ARPA> mike@BRL.ARPA (Mike Muuss) writes:
>It's unclear to me what effect you are trying to achieve.  Clearly, if

It sounds to me like the originator wants "our old friend" from last
month - the tty filter.

The idea is to come up with an interface that wraps around all processes,
and lets you describe how the input and output are to be changed.

For example, it would be nice to be able to say "if I type ESC<gap>3,
where <gap> is no longer than .5 seconds, send the sequence 'funky'",
or "if the output is _^H{x}, where {x} is any single character, change
that to ESC[3m{x}ESC[0m". This mechanism could handle interrupt sending
as well (if you really need asynchronous input like that).

Such an interface should handle multiple user-selectable modes, understand
raw and cbreak mode, and could incorporate editing capabilities (to get
that damn stuff out of the shells where it destroys my typeahead).

I designed such a system as a mental exercise (while bicycling to and
from work), and have all kinds of ideas on what is needed.
-- 
David Elliott		{decvax,ucbvax,ihnp4}!decwrl!mips!dce