From owner-freebsd-questions Sun Dec 13 10:35:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24976 for freebsd-questions-outgoing; Sun, 13 Dec 1998 10:35:52 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from goodall1.u.washington.edu (goodall1.u.washington.edu [140.142.12.163]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24971 for ; Sun, 13 Dec 1998 10:35:51 -0800 (PST) (envelope-from durang@u.washington.edu) Received: from localhost (durang@localhost) by goodall1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA168280; Sun, 13 Dec 1998 10:35:46 -0800 Date: Sun, 13 Dec 1998 10:35:46 -0800 (PST) From: "K. Marsh" To: Ben Smithurst cc: "q's" Subject: Re: bash echo turning off In-Reply-To: <19981213145404.C10841@scientia.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 13 Dec 1998, Ben Smithurst wrote: > K. Marsh wrote: > > > I'm having odd problems with bash, which I just began using a week back. > > Sometimes an x-term running bash will mysteriously stop echoing commands > > as I type them in. It still accepts commands and executes them, but I > > can't see them. > > $ stty echo > > should solve this. Perhaps you know this, and want to stop it happening > altogether, in which case I don't know. As you said, upgrading bash may > help. I've narrowed down the occurance of this problem. If I terminate man mid-page with ^C, then echo works for one more command, and then turns off. "stty echo" does turn it back on. I think an upgrade will fix it for good. Thanks! Kenneth J. Marsh University of Washington durang@u.washington.edu Chemical Engineering To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message