Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!cbatt!ihnp4!houxm!mtuxo!mtune!codas!peora!pesnta!wjvax!brett From: brett@wjvax.UUCP Newsgroups: comp.unix.wizards Subject: Re: stuff chars Message-ID: <781@wjvax.wjvax.UUCP> Date: Thu, 11-Dec-86 14:57:11 EST Article-I.D.: wjvax.781 Posted: Thu Dec 11 14:57:11 1986 Date-Received: Mon, 15-Dec-86 06:26:04 EST References: <19@houligan.UUCP> <2270@sdcsvax.UCSD.EDU> <104@quacky.UUCP> <775@wjvax.wjvax.UUCP> <107@quacky.UUCP> Reply-To: brett@wjvax.UUCP (Brett Galloway) Organization: Watkins-Johnson Co., San Jose, Calif. Lines: 27 In article <107@quacky.UUCP> dce@quacky.UUCP (David Elliott) writes: >In article <775@wjvax.wjvax.UUCP> brett@wjvax.UUCP (Brett Galloway) writes: >>In article <104@quacky.UUCP> dce@quacky.UUCP (David Elliott) writes: >>> >>>I have never found a way to change the handling of signals such that >>>input is not flushed. >> >>I think that you can use ^Y to embed a stop character in a typed-ahead >>input stream. >>-- > >I stand corrected, mainly because I didn't state my case correctly. >What I meant was that I know of no way to have a program generate >a signal that affects a process without flushing the input. (I've >been proven wrong...read on.) Actually, I think there is a way (besides the kludge ^Y). There is an undocumented local mode bit LNOFLSH which, when set, suppresses flushing upon keyboard signals. It is available as 'noflsh` in stty. If you do a stty noflsh, then interrupts won't flush input (or output for that matter). Suppressing flushing output is very useful for programs that do screen management and that trap keyboard signals; without it, the screen management can get trashed. -- ------------- Brett Galloway {pesnta,twg,ios,qubix,turtlevax,tymix,vecpyr,certes,isi}!wjvax!brett