From owner-freebsd-current Sun Sep 26 21:23:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from garnet.sover.net (garnet.sover.net [209.198.87.53]) by hub.freebsd.org (Postfix) with ESMTP id 18789152D7 for ; Sun, 26 Sep 1999 21:23:55 -0700 (PDT) (envelope-from adams@digitalspark.net) Received: from nightfall.digitalspark.net (arc0a169.bf.sover.net [209.198.85.169]) by garnet.sover.net (8.9.3/8.9.3) with ESMTP id AAA13011; Mon, 27 Sep 1999 00:23:48 -0400 (EDT) Comments: SoVerNet Verification (on garnet.sover.net) nightfall.digitalspark.net from arc0a169.bf.sover.net [209.198.85.169] 209.198.85.169 Mon, 27 Sep 1999 00:23:48 -0400 (EDT) Date: Mon, 27 Sep 1999 00:27:46 +0000 (GMT) From: Adam Strohl To: Benjamin Lewis Cc: current@FreeBSD.ORG Subject: Re: Wierd su problem still there In-Reply-To: <19990927033633.ED58027B@akira.bhlewis.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I too have encountered the same symptoms. I have no idea why this started > happening, but I have found a couple ways around it. First, two Control-Ds > will act as a Return if you find the status lines appearing. Second, the > stty command will fix it totally. I use `stty status ^T' to remap the status > command to Control-T rather than Control-J (the ^T is a carat, T): Damn, that works like a charm, but I wonder what is causing this to begin with. > I hope this helps, Yeah, good work around thanks :) - ----( Adam Strohl )------------------------------------------------ - - UNIX Operations/Systems http://www.digitalspark.net - - adams (at) digitalspark.net xxx.xxx.xxxx xxxxx - - ----------------------------------------( DigitalSpark.NET )------- - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message