From owner-freebsd-questions Sun Dec 13 22:54:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06371 for freebsd-questions-outgoing; Sun, 13 Dec 1998 22:29:00 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA06079 for ; Sun, 13 Dec 1998 22:27:40 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08867 for ; Mon, 14 Dec 1998 07:27:24 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19342 for ; Mon, 14 Dec 1998 07:27:23 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA07779 for freebsd-questions@FreeBSD.org; Mon, 14 Dec 1998 06:54:46 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:54:46 +0100 (CET) From: List User Message-Id: <199812140554.GAA07779@doorway.home.lan> To: freebsd-questions@FreeBSD.org Sender: owner-freebsd-questions@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.questions Path: root From: Graeme Tait Subject: Re: bash echo turning off Content-Type: text/plain; charset=us-ascii 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 To: "K. Marsh" Sender: owner-freebsd-questions@FreeBSD.ORG Content-Transfer-Encoding: 7bit Precedence: bulk Organization: Echidna Message-ID: <36745D2C.ABA@echidna.com> References: X-Mailer: Mozilla 2.02 (Win95; I) Delivered-To: vmailer-questions@freebsd.org X-Uidl: c10d5bdd437e1b44fad274524d071016 X-Loop: FreeBSD.ORG Mime-Version: 1.0 Cc: Ben Smithurst , "q's" Date: Mon, 14 Dec 1998 00:34:52 GMT 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message