Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!oliveb!intelca!mipos3!nate
From: nate@mipos2.intel.com (Nate Hess)
Newsgroups: comp.unix.wizards
Subject: Re: Character echo at read time
Summary: block on output
Keywords: echo tty device driver line discipline
Message-ID: <2848@mipos3.intel.com>
Date: 8 Sep 88 19:20:01 GMT
References: <347@spies.UUCP> <670025@hpclscu.HP.COM> <24355@bu-cs.BU.EDU> <4619@cbmvax.UUCP> <4477@mtgzz.att.com>
Sender: news@mipos3.intel.com
Reply-To: woodstock@sc.intel.com (Nate Hess)
Organization: Intel Corporation, Santa Clara, CA
Lines: 22
In-reply-to: dam@mtgzz.att.com (d.a.morano)

In article <4477@mtgzz.att.com>, dam@mtgzz (d.a.morano) writes:
>Also, on UNIX(TM), the echoed 
>characters can get displayed in the middle of a write(2) to the terminal.  
>This serves to destroy background escape sequences that may be printing 
>to the terminal from a background process using write(2) directly.  The 
>resulting effect is garbage on the terminal display.

A simple, straight-forward, and beneficial solution to the problem of
background jobs writing garbage to the screen is to do

stty tostop

which will cause background jobs to stop on output, just as they do by
default for input.  This is especially handy for background find
commands, etc.

Your mileage may vary,
--woodstock
-- 
	   "What I like is when you're looking and thinking and looking
	   and thinking...and suddenly you wake up."   - Hobbes

nate@mipos3.intel.com     ...!{decwrl|hplabs!oliveb|amd}!intelca!mipos3!nate