Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!ateng!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.unix.wizards Subject: Re: csh / bsd job control Message-ID: <260A8D0F.4BAF@tct.uucp> Date: 23 Mar 90 20:54:39 GMT References: <22821@adm.BRL.MIL> <100777@convex.convex.com> Organization: ComDev/TCT, Sarasota, FL Lines: 17 According to tchrist@convex.COM (Tom Christiansen): >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. This is almost what tcsh does; I like it. Tcsh doesn't try to restore modes. Instead, it notes *changes*. It obeys the sane ones for command line editing while leaving the rest in place for other hapless applications. :-) For example, "stty erase '^?'" affects the tcsh backspace operation, but "stty -echo" doesn't. However, the "stty -echo" *will* affect other programs. No, it's not perfect, but at least it prevents weird modes that keep you from typing "stty sane". -- Chip Salzenberg at ComDev/TCT , "The Usenet, in a very real sense, does not exist."