Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!convex!convex.COM
From: tchrist@convex.COM (Tom Christiansen)
Newsgroups: comp.unix.wizards
Subject: Re: csh / bsd job control
Message-ID: <100777@convex.convex.com>
Date: 22 Mar 90 15:16:00 GMT
References: <22821@adm.BRL.MIL>
Sender: news@convex.com
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Software Development, Richardson, TX
Lines: 20

In article <22821@adm.BRL.MIL> bzs@cs.bu.edu (Barry Shein) writes:
>I'd be curious to hear how those shells that do this handle the stty
>problem.

I think the best thing to do is to have the shell always restore
the mode to what it was before the program was called, irrespective
of whether the program should have stopped, exited, or aborted.  
In order to handle the stty case, you can introduce a variable to 
control this, in the style of noglob and nonomatch.  Let's call
this noreset.  Thus, 
	% set noreset; stty kill ^g; unset noreset
I've actually worked with (t?)csh's that had this feature,
but I don't recall precisely where.

--tom
--

    Tom Christiansen                       {uunet,uiucdcs,sun}!convex!tchrist 
    Convex Computer Corporation                            tchrist@convex.COM
		 "EMACS belongs in <sys/errno.h>: Editor too big!"