From: Warner Losh (imp@boulder.parcplace.com)
Date: 02/28/93


From: imp@boulder.parcplace.com (Warner Losh)
Subject: Re: NEW: Patch to implement ^T process status feature
Date: Sun, 28 Feb 1993 07:11:36 GMT

In article <1993Feb27.163045.19553@wam.umd.edu> joel@wam.umd.edu (Joel
M. Hoffman) writes:
>What happens when a user program uses ^T (e.g., the shell, emacs,
>nethack, etc.)? Who sees the ^T, the kernel or the app? If the app.,
>a broken app. will kill the feature, and if the kernel, you'll break
>common apps. What I would recommend is using some >unused< key for
>process status. (Alt-PgUp, eg. -- I've never used that one before.)

After looking at the patch and some commentary that I got from the
author, it appears that in raw mode this feature is disabled, so emacs
should work OK. It also prints the information on SysReq (or
something like that). Keep in mind that there is no ASCII character
that corresponds to many of the keys on they keyboard, so it has to be
something that both local and remote users can type. It also has to
be something that will work inside of X windows. ^T seems reasonable
enough to me, but I'd like to see that under user control somehow.

This is also how it worked on TOPS-20, VMS, and RSTS/E.

Warner

-- 
Warner Losh             imp@boulder.parcplace.COM       ParcPlace Boulder
I've almost finished my brute force solution to subtlety.