Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Fri, 11 Apr 2003 13:02:29 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Garry Heaton <garry AT heaton6 DOT freeserve DOT co DOT uk>
cc: cygwin AT cygwin DOT com
Subject: Re: Limited remote terminal access via cygwin
In-Reply-To: <3E96EF13.4020603@heaton6.freeserve.co.uk>
Message-ID: <Pine.GSO.4.44.0304111254150.26381-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 11 Apr 2003, Garry Heaton wrote:

> Igor Pechtchanski wrote:
> > On Fri, 11 Apr 2003, Garry Heaton wrote:
> >>Igor Pechtchanski wrote:
> >>>On Fri, 11 Apr 2003, Garry Heaton wrote:
> >>>>Reid Thompson wrote:
> >>>>
> >>>>>after you login to your remote box run one of the following commands
> >>>>>   export TERM=xterm
> >>>>>or
> >>>>>   export TERM=vt100
> >>>>>or
> >>>>>   export TERM='whatever term type you normally use & is recognized on
> >>>>>the remote system"
> >>>>>reid
> >>>>>
> >>>>>>-----Original Message-----
> >>>>>>From: Garry Heaton [mailto:garry AT heaton6 DOT freeserve DOT co DOT uk]
> >>>>>>Sent: Friday, April 11, 2003 7:46 AM
> >>>>>>To: Cygwin
> >>>>>>Subject: Limited remote terminal access via cygwin
> >>>>>>
> >>>>>>I'm setting-up headless Linux/SAMBA servers for use in
> >>>>>>Windows office networks which I want to admin from Windows
> >>>>>>via Cygwin. When I 'ssh' into the Linux box from Cygwin I
> >>>>>>only have limited terminal access. When I try to launch emacs
> >>>>>>on the remote machine I get the response:
> >>>>>>
> >>>>>>emacs: Terminal type cygwin is not defined.
> >>>>>>
> >>>>>>When I examine files using 'less' I also receive the message:
> >>>>>>
> >>>>>>WARNING: terminal is not fully functional
> >>>>>>
> >>>>>>With 'less' the Cygwin/Windows terminal only displays a fixed
> >>>>>>% of the file examined and will not scroll to the end.
> >>>>>>
> >>>>>>My Cygwin environment settings are:
> >>>>>>
> >>>>>>ntsec check_case:strict tty
> >>>>>>
> >>>>>>Garry Heaton
> >>>>
> >>>>Tried all of these but nothing worked. I'm not running X on Cygwin. Just
> >>>>console mode. Still can't scroll past the first screen of an opened file.
> >>>>Emacs-nox also has display problems.
> >>>>
> >>>>Garry
> >>>
> >>>Garry,
> >>>
> >>>TERM should reflect the terminal you're running *in* (the one you use to
> >>>ssh to the Windows machine).  Normally, ssh will inherit the TERM setting
> >>>from the invoking shell.  If something resets the TERM value (I'm guessing
> >>>your ~/.bashrc or ~/.bash_profile), you'll need to fix that (e.g., by
> >>>putting a "[ -z TERM ]" guard).
> >>>
> >>>Try invoking "bash --login -v" from ssh to see if a TERM=... command is
> >>>executed.
> >>>      Igor
> >>
> >>I'm not 'ssh'-ing into the Windows machine. I'm running Cygwin on the
> >>Windows machine to admin a Linux server. So far running emacs-nox produces
> >>faulty screen output. 'less' also has some problems.
> >>
> >>Garry
> >
> > Ah, I misread it.  Sorry.
> >
> > You can do one of three things:
> >
> > 1) Use an XTerm or an RXVT window to ssh.  That way, your TERM value will
> > be known on Linux.  FYI, rxvt can be used without X on Cygwin.
> > 2) Set your TERM in the bash (command) window to something Linux will
> > recognize and that is compatible with the console handler (I *think*
> > "xterm" should work, but you'll have to try and see).  FYI, "cygwin" is
> > not compatible with "vt100", AFAIK.
> > 3) Make your Linux machine understand the "cygwin" TERM value by copying
> > over /usr/share/terminfo/c/cygwin and the relevant part of /etc/termcap
> > (for older apps).
> >
> > #3 is the "right way" of fixing your problem, but may be more trouble than
> > it's worth.
> >       Igor
>
> Thanks, Igor. #3 fixed everything. How about /etc/termcap? Surely I can't
> overwrite the Linux version. It's a huge file.
> Garry

Garry,

Note that I said "the relevant part of /etc/termcap".  It's a text file,
you could simply append the "cygwin:..." part to your Linux /etc/termcap.
There's probably a program to do it automatically, anyway ("tic -C" comes
to mind).  You could also get Charles Wilson's terminfo source entry for
"cygwin" from <http://cygwin.com/ml/cygwin/2003-04/msg00187.html>, and use
"tic -C" to compile it to termcap format.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Knowledge is an unending adventure at the edge of uncertainty.
  -- Leto II


--
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/