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 Date: Thu, 8 Mar 2001 00:03:43 +0200 Message-Id: <200103072203.AAA14453@linux.> From: "Ehud Karni" To: toddw AT wrq DOT com Subject: Re: cygwin / ssh / emacs term type issue CC: help-gnu-emacs AT gnu DOT org, cygwin AT sources DOT redhat DOT com In-reply-to: <1654BC972546D31189DA00508B318AC80343E48B@charmander.wrq.com> (message from Todd Wells on Wed, 7 Mar 2001 11:13:56 -0800) Organization: Simon & Wiesel Insurance agency Reply-to: ehud AT unix DOT simonwiesel DOT co DOT il References: <1654BC972546D31189DA00508B318AC80343E48B AT charmander DOT wrq DOT com> X-Mailer: Emacs 20.7.1 rmail (send-msg 1.104) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 7bit On Wed, 7 Mar 2001 11:13:56 -0800, Todd Wells wrote: > > I'm running cygwin bash on Win2k. While running cygwin I use ssh to connect > to both linux and solaris machines. When I attempt to run emacs -nw on the > remote machines, I get this: > > bash-2.03$ emacs -nw my_filename > emacs: Terminal type cygwin is not defined. > If that is not the actual type of terminal you have, > use the Bourne shell command `TERM=... export TERM' (C-shell: > `setenv TERM ...') to specify the correct type. It may be necessary > to do `unset TERMINFO' (C-shell: `unsetenv TERMINFO') as well. > > Since in this case I'm not actually running emacs on the Win2k machine, the > traditional FAQ answer for NT emacs/cygwin integration don't seem to apply. > For grins I tried export TERM=vt100, but that emulation mode didn't seem ssh > compatible and I got unpredictable results. Emacs is telling you its problem: 1. Your terminal type (that it got from the connecting telnet thru the ssh) is cygwin. This is correct ! 2. You don't have the cygwin terminal description on the (remote) system. BTW. The ssh is just a transparent pipe, It does not affect the terminal attributes at all. The obvious solution - compile (or copy) the cygwin terminal definition. Way 1 - Copying the binary (compiled) terminal description. The binary is found (on the PC) at /usr/share/terminfo/c/cygwin you need to copy it to the same location on the linux. Check the man page of "terminfo" for the exact file name on the solaris. You need root permission to put it on linux/solaris. Way 2 - Uncompile and re-compile. 2.1 On the PC do: infocmp -I -1 cygwin > cygwin.src 2.2 On the UNIX do: tic -v cygwin.src If you run 2.2 as root the definition will be system wide, otherwise it will be installed in your home directory ($HOME/.terminfo). If you don't have root privileges, ask your sysadmin to install the cygwin terminal description (I think s/he'll want the source from 2.1). You are encouraged to read the `terminfo' man page to understand what is terminal description and what it (may) contain. You should also thank Chuck Wilson for his porting of ncurses to Cygwin that made this possible. May be he will add something about exporting the `cygwin' terminal data to the ncurses readme. Ehud. -- @@@@@@ @@@ @@@@@@ @ @ Ehud Karni Simon & Wiesel Insurance agency @ @ @ @@ @ Tel: +972-3-6212-757 Fax: +972-3-6292-544 @ @ @ @ @ @@ (USA) Fax and voice mail: 1-815-5509341 @ @ @ @ @ @ Better Safe Than Sorry http://www.simonwiesel.co.il mailto:ehud AT unix DOT simonwiesel DOT co DOT il -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple