From owner-freebsd-questions Sun Dec 13 16:33:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03811 for freebsd-questions-outgoing; Sun, 13 Dec 1998 16:33:54 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from hera.webcom.com (hera.webcom.com [209.1.28.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03806 for ; Sun, 13 Dec 1998 16:33:53 -0800 (PST) (envelope-from graeme@echidna.com) Received: from eresh.webcom.com (eresh.webcom.com [209.1.28.49]) by hera.webcom.com (8.9.1/8.9.1) with SMTP id QAA08139; Sun, 13 Dec 1998 16:33:38 -0800 Received: from [209.122.117.150] by inanna.webcom.com (WebCom SMTP 1.2.1) with SMTP id 15595669; Sun Dec 13 16:31 PST 1998 Message-Id: <36745D2C.ABA@echidna.com> Date: Sun, 13 Dec 1998 19:34:52 -0500 From: Graeme Tait Organization: Echidna X-Mailer: Mozilla 2.02 (Win95; I) Mime-Version: 1.0 To: "K. Marsh" Cc: Ben Smithurst , "q's" Subject: Re: bash echo turning off References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG K. Marsh wrote: > > 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! I have noticed almost exactly the same problem, but when connected to a remote system via telnet. In this case, echo is lost immediately after ^C out of man. The same system used in console mode locally is fine, but if I telnet to localhost, the problem occurs. I though it was something I needed to RTFM for, so hadn't asked here. "stty echo" fixes it - previously I was having to log out and back in again. This is true with 2.2.7S (7-15-98) and 2.2.6R, and I don't think it's confined to bash - I got the same problem in csh, but not sh. So I'm not sure an upgrade is the solution, unless there's been a recent change. Is this a bug? I have also been quitting "man" with ^C, but just realized that as "man" uses "more" as the default pager, you can quit with "q". This seems to avoid the problem of loss of echo. -- Graeme Tait - Echidna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message