This is the mail archive of the
mailing list for the Cygwin project.
Re: problem with cygwin box (termcap?)
On Wed, Sep 22, 2004 at 02:58:20PM -0700, Brian Dessent wrote:
>David Arnstein wrote:
>> I launch a cygwin "box" (command window) on my Windows 2000 machine.
>> I run ssh to connect to a shell account running a variant of BSD Unix.
>> Whenever I use the program "less" on that shell account, it complains
>> "WARNING: terminal is not fully functional."
>> Another user has stated that tin (the news reader) complains
>> "tin: Terminal must have clear to end-of-screen (cd)
>> I suspect that these issues are related. Can the termcap entry for
>> cygwin be improved? Or is this truly a limitation of the cygwin box?
>You could also just use rxvt instead of of a cmd.exe window, which
>should result in $TERM being set to "rxvt" which should be recognised
>everywhere. If for whatever reason you must use cmd.exe then follow the
>advice already in the thread to add the "cygwin" terminal info to the
>database on the remote end.
Also, the "ansi" or "vt100" TERM types may work acceptably on the remote
system depending on what the application is trying to do.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html