This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Limited remote terminal access via cygwin]
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
--
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/