Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Dec 1998 06:54:46 +0100 (CET)
From:      List User <listuser@netspace.net.au>
To:        freebsd-questions@FreeBSD.org
Message-ID:  <199812140554.GAA07779@doorway.home.lan>

next in thread | raw e-mail | index | archive | help
Newsgroups: freebsd.questions
Path: root
From: Graeme Tait <graeme@echidna.com>
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" <durang>
Sender: owner-freebsd-questions@FreeBSD.ORG
Content-Transfer-Encoding: 7bit
Precedence: bulk
Organization: Echidna
Message-ID: <36745D2C.ABA@echidna.com>
References: <Pine.A41.3.95b.981213102758.167422B-100000@goodall1.u.washington.edu>
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 <ben>, "q's" <freebsd-questions>
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812140554.GAA07779>