Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "David Christensen" To: , Subject: RE: Cygwin, ssh, and top Date: Sat, 15 Oct 2005 18:01:14 -0700 Message-ID: <002601c5d1ed$1d0e06c0$0a01a8c0@p42800e> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: <435188AC.DF0D9015@dessent.net> X-IsSubscribed: yes Brian Dessent wrote on cygwin: > You're setting TERM before connecting? Yes. > Have you verified that the setting is indeed changed once you are > logged on to the remote? Yes. > You might try "vt102" as well. Also, consider using rxvt with Cygwin I prefer that the machines I log into work correctly with Cygwin ssh and TERM=cygwin. Debian 3.1 is only slightly broken. My hosting provider uses an internally customized distribution based on Slackware; Cygwin ssh is just one of many issues. > if you are using the stock CMD.EXE window. I use Cygwin Bash. > I suspect it has something to do with the lines/columns settings. > Try resizing the window before running top to make it recalculate > size. Or run something like "eval `resize`". Again, my preference is that the sshd host work correctly with the Cygwin ssh client. David -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/