Path: utzoo!attcan!uunet!snorkelwacker!mit-eddie!aryeh
From: aryeh@eddie.mit.edu (Aryeh M. Weiss)
Newsgroups: comp.unix.wizards
Subject: Re: csh / bsd job control
Message-ID: <1990Mar23.152715.5958@eddie.mit.edu>
Date: 23 Mar 90 15:27:15 GMT
References: <22821@adm.BRL.MIL> <KARL.90Mar21140133@giza.cis.ohio-state.edu>
Reply-To: aryeh@eddie.MIT.EDU (Aryeh M. Weiss)
Organization: MIT EE/CS Computer Facilities, Cambridge, MA
Lines: 22

In article <KARL.90Mar21140133@giza.cis.ohio-state.edu> karl_kleinpaste@giza.cis.ohio-state.edu writes:
...
>Not really...
>
>   I'd be curious to hear how those shells that do this handle the stty
>   problem.
>
>The SysV csh I built took care of the problem reasonably trivially.
>When a job _stopped_, csh would restore the tty state it knew before
>the job was started.  When the job was restarted, csh would re-assert
>the tty state it had when the job last stopped.
>
>When a job _ended_, the tty state was not messed with, on the
>assumption that the job knew what it was doing if it changed things.
>
Csh already has "prefixes" like "nohup `command'" or "time `command'".
How about a prefix like "condom `command'", which would save the tty state 
before the command is run and restore it after to a "safe" state (:-).
This would be useful for debugging software that changes the tty state
but may still be prone to crash before it gets a chance to restore the modes.

--