Xref: utzoo comp.unix.questions:16467 comp.unix.wizards:18280 Path: utzoo!attcan!utgpu!watmath!att!dptg!rutgers!apple!oliveb!mipos3!td2cad!brister From: brister@td2cad.intel.com (James Brister) Newsgroups: comp.unix.questions,comp.unix.wizards Subject: Re: Putting a curses program in the background then in the foreground Message-ID: Date: 21 Sep 89 23:19:41 GMT References: <4013@augusta.UUCP> Sender: news@td2cad.intel.com Followup-To: comp.unix.questions Organization: Intel Corp., Santa Clara, CA, USA Lines: 14 In-reply-to: rcostell@augusta.UUCP's message of 21 Sep 89 11:58:15 GMT My guess about this sort of required behaviour is this: i) the program catches the SIGTSTP signal. In the handler it reset the terminal characteristics and then sends itself a SIGSTOP. ii) the program catches the SIGCONT signal. In the handler it does a refresh of the necessary stuff and then continues. There's probably a few minor :-) details in there that need to be added. Comments? James -- James Brister brister@td2cad.intel.com Intel Corp. {decwrl,oliveb}!td2cad!brister