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 Date: Thu, 26 Dec 2002 12:11:27 +1100 From: Mark Ord To: cygwin AT cygwin DOT com Subject: Re: problem with vi over ssh Message-ID: <20021226011127.GA980121@chimera.home> References: <1040826081 DOT 19676 DOT ezmlm AT cygwin DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1040826081.19676.ezmlm@cygwin.com> User-Agent: Mutt/1.4i Mirza, > i noticed a problem with vi when i connect to a linux. i found no > answers about this problem anywhere: i start my cygwin and connect > over ssh to a linux machine. when i want to open a file using vi -> > vi file_name, i get the following: [..snip..] > i am having this problem only if i use cygwin. > > any ideas? or is this normal? A Linux machine knows nothing about the terminal type 'cygwin'. This is normal. You'll also only really experience this when sshing from a console window - if you ssh from rxvt (term = xterm) everything should be fine. If, however, you want to ssh in a console window, simply add some explicit term setting in your startup file on the remote server. For example, I have in .bashrc: # Cygwin term type is unrecognised, and sucks on Linux, so if ssh'ing from # a console window, set the term to something that works nicely. if [ "$TERM" == "cygwin" ]; then export TERM=vt100 fi Or add the appropriate syntax to the appropriate file if you use a different shell. HTH, Mark. -- Mark Ord | "We always have music playing, Melbourne, Australia | it's up to us to hear it as mailto://ord AT alphalink DOT com DOT au | bosanova..." http://www.alphalink.com.au/~ord/home/ | - Roger Clyne - -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/