Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Jonadab the Unsightly One" Organization: There is no organisation. To: cygwin AT cygwin DOT com Date: Wed, 20 Jun 2001 18:07:42 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Editor to use with ssh'ing into NT server? Reply-to: jonadab AT bright DOT net Message-ID: <3B30E66E.9972.2167B50@localhost> In-reply-to: <549AB966B45DD311A58A0000E86CEA8D0CAED5F2@postoffice.btitele.com> X-Eric-Conspiracy: My name is not Eric. X-Platform: Windows '95 OSR2 (heavily adjusted and customised) X-mailer: Pegasus Mail for Win32 (v3.12) # I have set TERM to just about everything I can think of # # vt100 # ansi # cygwin Try setting it to linux I don't know why this works (or whether it will work in your case), but I was able to get some things through ssh (shelling into my Linux box from cygwin) to work this way that refused otherwise, including Emacs. What really bugs me is that ansi doesn't work, but I found that it didn't work for me, running Emacs on the linux box from a cygwin ssh session. Setting term to linux solved this. *shrug* Whatever works. # but I do not get any better results. # # vim starts up, but the keyboard mappings are wrong. [Going OT] Another possibility, if you're on a LAN, is to use Samba to edit files; that way you can use an editor on the client to edit files on the host. If you're coming in over the internet or have relevant security issues, this may not be an option. -- jonadab -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple