On 2004.02.16 12:20, Richard Crawford wrote:
> Whenever I ssh into my Debian box, Lucien, with Cygwin from a Windows
> computer and try to execute Vi or top or similar tools, I get an error
> like the following:
>
> Unknown terminal "cygwin" in $TERM
>
> Naturally, this doesn't happen when I S
Jennifer
I use FreeBSD Current - We had a similar problem when the new KDE hit the ports tree. There are issues with conflicts because features have moved between libraries and that is causing conflicts. You have three choices - wait until other people sort out the error and a better system gets
Mark K. Kim wrote:
You can fix this several ways. For simplicity sake, you probably wanna
set your terminal type to ansi if it's "cygwin" from .bashrc in your
debian box:
if [ "$TERM" = "xcygwin" ]
then
export TERM=ansi
fi
Assuming, of course, you're using Bash.
That worked perfectly.
You can fix this several ways. For simplicity sake, you probably wanna
set your terminal type to ansi if it's "cygwin" from .bashrc in your
debian box:
if [ "$TERM" = "xcygwin" ]
then
export TERM=ansi
fi
Assuming, of course, you're using Bash.
Other alternatives: The proper thing to d
Whenever I ssh into my Debian box, Lucien, with Cygwin from a Windows
computer and try to execute Vi or top or similar tools, I get an error
like the following:
Unknown terminal "cygwin" in $TERM
Naturally, this doesn't happen when I SSH into my Red Hat computers.
How do I fix this issue so th
