From owner-freebsd-questions@FreeBSD.ORG Wed Sep 24 07:22:59 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29D2C106564A for ; Wed, 24 Sep 2008 07:22:59 +0000 (UTC) (envelope-from chris@smartt.com) Received: from barium.smartt.com (barium.smartt.com [69.67.187.30]) by mx1.freebsd.org (Postfix) with ESMTP id 14E548FC19 for ; Wed, 24 Sep 2008 07:22:58 +0000 (UTC) (envelope-from chris@smartt.com) Received: from [69.31.165.110] (erx208b165110.smarttadsl.com [69.31.165.110]) by barium.smartt.com (Postfix) with ESMTPA id 2F51310E421; Wed, 24 Sep 2008 00:22:38 -0700 (PDT) Message-ID: <48D9EACB.9070107@smartt.com> Date: Wed, 24 Sep 2008 00:22:51 -0700 From: Chris St Denis User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: Andreas Davour References: <48D98542.6090007@smartt.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-questions@freebsd.org" Subject: Re: Fix corrupted terminal output X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2008 07:22:59 -0000 Andreas Davour wrote: > On Tue, 23 Sep 2008, Chris St Denis wrote: > >> Occasionally, I accidentially cat a binary file or a directory casing >> the terminal output to be corrupted with text looking like (don't >> know if this will make it through the mail cleanly) >> >> E???? ??? ?? ?????????. >> ????2# >> >> >> To fix this normally I just close the window and open a new ssh >> connection, but I am wondering if there is a more clean way to do >> this. I've tried reset(1), but it doesn't seem to help any. > > What termnial emulator are you using? KDE Konsole have an "Edit->Reset > & Clear Terminal" menu alternative that usually manages to clear such > problems up for me. > > /Andreas > I use putty ssh client (on windows). I had thought it was a console change rather than terminal editor specific. I'll try the things people have suggested here next time it happens. Thanks for the suggestions.