Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!purdue!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.unix.wizards
Subject: Re: csh / bsd job control
Message-ID: <12413@smoke.BRL.MIL>
Date: 23 Mar 90 08:17:10 GMT
References: <22821@adm.BRL.MIL> <100777@convex.convex.com>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 12

In article <100777@convex.convex.com> tchrist@convex.COM (Tom Christiansen) writes:
>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 ...

Yup, that's how we do it in the BRL shell when command-line editing
(and history) are enabled.  As to stty, we simply made it a builtin
that merely invoked the real one but keeps track of the new non-prompt
tty state that results.  The way I actually look at it is that the
"vanilla" tty state is established for programs that are executed,
the "fancy" state is (of necessity) exactly that which the shell needs
for its own (command-line editing and job control) purposes, and "stty"
changes the "vanilla" state only.