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: Cc: Subject: RE: Cygwin, ssh, and top Date: Sun, 16 Oct 2005 13:06:24 -0700 Message-ID: <004001c5d28d$1b076ba0$0a01a8c0@p42800e> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <435274C0.50209@acm.org> X-IsSubscribed: yes David Rothenberger wrote on cygwin: > Try setting COLUMNS to 79 with the comment "export COLUMNS=79". > I had this problem when I ran the Cygwin ssh client from bash *in a > CMD.EXE window*. For some reason, Debian miscalculated the COLUMNS > size; it was 1 column too large. When I manually set COLUMNS (from > 130 to 129 in my case), top worked correctly. > I recommend running ssh from bash in an rxvt window instead of using > the CMD.EXE window. This will give you an "xterm" terminal in Debian > which will work much better. I use it all the time with Debian 3.1 > and have no problems. Invoking rxvt from a Cygwin Bash shell and then ssh'ing into Debian and customized Slackware gives me the same results as Putty -- e.g. everything works on Debian 3.0 and 3.1, and the customized Slackware is messed up. My preference is still that Cygwin bash ssh work correctly with Debian 3.1, and I believe the problem is with whatever package provides terminal stuff in Debian 3.1. I'll try to find the package and file a bug report. 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/