From owner-freebsd-bugs Tue Oct 20 13:27:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29063 for freebsd-bugs-outgoing; Tue, 20 Oct 1998 13:27:45 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29053 for ; Tue, 20 Oct 1998 13:27:42 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id OAA05955; Tue, 20 Oct 1998 14:27:14 -0600 (MDT) Message-Id: <4.1.19981020142239.06c13d50@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 20 Oct 1998 14:23:27 -0600 To: bugs@FreeBSD.ORG From: Brett Glass Subject: No terminal echo after certain commands Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After executing certain shell commands in FreeBSD's csh (especially ones involving "more"), I sometimes find that characters don't echo. This most frequently occurs when I ^C out of something that's scrolling text through more, but also occurs at other times. To get the system to echo what I type, I have to use the command "tset ". This problem occurs both at the main system console (I'm not using VT100 emulation; just plain old cons25) and during telnet sessions. The systems on which I've seen this problem range from 2.1.5 to 2.2.7-RELEASE. Have others seen this? Is there a fix? --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message