Re: terminal capability problem when login therough screen

[Pia Mikeal]

I usually just put something like the following in my .profile on remote 
servers

export TERM=vt100

because your problem is that the remote box does not know about the 
terminal type that your local screen sets it to.  The reason I do this on 
a case by case basis rather than putting it in the local .screenrc is 
because I usually want to take advantage of the terminal settings I have 
in my local screen, but some of my servers only support vt100

HTH,

Pia


On Thu, 17 Dec 2009, J. Bakshi wrote:

> Hello list,
>
> A strange issue which I encounter during ssh through screen. If I ssh to
> my remote servers ( one debian and one suse) I have no problem at all to
> use vim. But if I  *ssh through screen* then the vim on remote debian
> box reports
>
> ` ` `
> E558: Terminal entry not found in terminfo
> 'screen.rxvt' not known. Available builtin terminals are:
>    builtin_riscos
>    builtin_amiga
>    builtin_beos-ansi
>    builtin_ansi
>    builtin_pcansi
>    builtin_win32
>    builtin_vt320
>    builtin_vt52
>    builtin_xterm
>    builtin_iris-ansi
>    builtin_debug
>    builtin_dumb
> defaulting to 'ansi'
>
> ` `
>
> where the remote suse box reports
>
> ` ` `
> E437: terminal capability "cm" required
> Press ENTER or type command to continue
> ` ` `
>
> Can I add some code in  my .screenrc to resolve this problem ?
> Please suggest.
> Thanks
>
>
>
> _______________________________________________
> screen-users mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/screen-users

Pia Mikeal
System Administrator
Markey Center for Structural Biology
Purdue University
address@hidden
(765)496-6781