Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!ginosko!brutus.cs.uiuc.edu!psuvax1!gatech!ncar!tank!shamash!nic.MR.NET!umn-cs!nis!pwcs!stag!syntel!dal
From: dal@syntel.mn.org (Dale Schumacher)
Newsgroups: comp.os.minix
Subject: Re: Important new program: cleanit.c
Message-ID: <091189A6470@syntel.mn.org>
Date: 11 Oct 89 22:48:18 GMT
Reply-To: dal@syntel.mn.org (Dale Schumacher)
Lines: 21
X-Member-Of: STdNET (ST Developer's Network)

rbthomas@athos.rutgers.edu (Rick Thomas) writes...
> What I have in mind is the ability to be working away on something that
> can't be interrupted and I get an idea that I want to try out, so I hit
> some key combination like, say, <alt>-F1 and the current screen image
> is saved away in a RAM buffer.  The executing program continues to
> execute, but it will be put into io-wait state if it attempts to print
> to the screen or read from the keyboard.

My implementation doesn't suspend the other virtual terminals when you
switch.  The screen can still be written to even if it is not the one
currently being displayed.  The keyboard focus is, of course, always tied
to the currently visible screen.  If you don't want to miss any output
while you're looking at another screen, simply ^S (XOFF) the screen
before you leave and ^Q (XON) when you get back.  I'm not talking about
theory here, I actually have this working on the ST.

\\   /  Dale Schumacher                         399 Beacon Ave.
 \\ /   (alias: Dalnefre')                      St. Paul, MN  55104-3527
  ><    ...umn-cs!midgard.mn.org!syntel!dal     United States of America
 / \\   "What is wanted is not the will to believe, but the will to find out,
/   \\  which is the exact opposite." -Bertrand Russell