Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Sun, 29 Oct 2000 14:32:41 -0330 (NST)
From: Neil Zanella <nzanella AT cs DOT mun DOT ca>
To: Cygwin Mailing List <cygwin AT sourceware DOT cygnus DOT com>
cc: ncurses <bug-ncurses AT gnu DOT org>
Subject: question about cygwin terminal type
Message-ID: <Pine.OSF.4.21.0010291423020.6928-100000@garfield.cs.mun.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


Could someone please explain to me what the cygwin terminal type is all
about? If I telnet to a Sun workstation from Win2K with the supplied
telnet program then the default terminal type is ansi. But if I click
on the cygwin icon then ssh to a remote Sun computer then the default
terminal window for Win2K (which looks the same as the one I get when I
launch telnet) carries a cygwin terminal type. Now the white on
black terminal emulation program that ships with Win2K is different than
the black on white one that used to come on NT and Win95/98 and perhaps
that's not the only thing that's changed. So after enterning a remote
shell do I have to change my terminal type to asni or should I leave it
as cygwin? The problem I had lately is that SIGWINCH did not seem to
propagate well but that's another issue altogether I suppose.

Thanks,

Neil


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com