Hi,
On Wed, Dec 7, 2016 at 3:25 PM, Cameron Simpson <cs@xxxxxxxxxx> wrote:
> On 07Dec2016 10:34, Alex <mysqlstudent@xxxxxxxxx> wrote:
>>>
>>> How do I either add the new terminal type to the remote system, or
>>> change my terminal type locally so it corresponds with one that's
>>> available on the remote system?
>>>
>>> # echo $TERM
>>> screen.xterm-256color
>>
>>
>> I should have added that I'm aware that I can just change the terminal
>> type by just changing the TERM environment variable to something like
>> vt100 or xterm (export TERM=vt100), but I'm looking for the real
>> solution here to take full advantage of the screen.xterm-256color
>> terminal type on the remote system.
>
>
> As you say the quick hack is to use another name. I use "xterm-256color" for
> iTerms.
>
> However, you can just keep a personal copy of the terminfo file for your
> terminal; copy your local system's one to your remote system. I keep
> personal copies of a few things, and have this in my shell startup:
>
> # Make sure we have a useful definition.
> unset TERMCAP TERMINFO
> case "$TERM" in
> e-adm3a|e-adm3a-fi|xterm*|trs80*|qvt311gx|amiga|amiga-fterm)
> [ -r $HOME/rc/term/cap ] && { TERMCAP=$HOME/rc/term/cap; export
> TERMCAP; }
> [ -d $HOME/rc/term/info ] && { TERMINFO=$HOME/rc/term/info; export
> TERMINFO; }
> ;;
> esac
>
> The terminfo directory has a subdir for each terminal's leading letter, with
> the file inside that. See terminfo(5).
Copying the screen.xterm-256color terminfo entry to the remote system
into /usr/share/terminfo/s/ directory fixed the problem.
Thanks everyone for all your help.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
