thats just how it is ..it depends on what "xterm" you use, I use
gnome-terminal(used to use kvt) and don't have a problem. This SGI Indy
I'm on set's it's default terminal to iris-ansi. Slackware (3.2
anyways) had in the /etc/profile a detection routine for terminal type and
if it failed detectio
*- On 23 Dec, Andrew J.F. Clark wrote about "TERM=xterm-debian"
> Whenever I use ssh (I'm not sure about telnet) to connect to the
> slakware boxes at work through an xterm or rxvt and try to use pine and
> pico etc, I get an error about unknown terminal xterm-debian (or rxvt).
> I can solve this
"Andrew J.F. Clark" <[EMAIL PROTECTED]> writes:
| Whenever I use ssh (I'm not sure about telnet) to connect to the
| slakware boxes at work through an xterm or rxvt and try to use pine and
| pico etc, I get an error about unknown terminal xterm-debian (or rxvt).
| I can solve this by export TERM=x
From the X-Strikeforce (debian port) page
(http://www.debian.org/~branden/) heading xterm and the keyboard.
xterm and the keyboard
Debian has modified the key translations that xterm uses to make its
behavior more consistent with the Linux virtual
console. This has been achieved by setting th
*- On 19 Aug, Andy Spiegl wrote about "TERM=xterm-debian and other
distributions"
> Hi!
>
> Everytime I log into a non Debian system I have to set the
> TERM variable to xterm or vt100 manually, because the system
> doesn't know "xterm-debian" of course
>
> I don't think this was intended, so I
5 matches
Mail list logo