tmux and screen-256 TERM not supported on remote hosts

up vote
30
down vote

favorite

I have set up my tmux to use screen-256colors and it works great with vim.

However, when I ssh to a remote host from within tmux, screen-256colors isn't recognized, so I'm getting errors like this:

E558: Terminal entry not found in terminfo 'screen-256color' not known. Available builtin terminals are:

    builtin_ansi

    builtin_xterm

    builtin_iris-ansi

    builtin_dumb defaulting to 'ansi'

Other than editing each remote .bashrc (similarly to this suggestion), is there any way to set the TERM correctly and automatically on the remote host?

edited Mar 20 '17 at 10:17

Community♦

asked Jun 2 '12 at 20:45

Yoav Aner

3251510

add a comment |

up vote
30
down vote

favorite

I have set up my tmux to use screen-256colors and it works great with vim.

However, when I ssh to a remote host from within tmux, screen-256colors isn't recognized, so I'm getting errors like this:

E558: Terminal entry not found in terminfo 'screen-256color' not known. Available builtin terminals are:

    builtin_ansi

    builtin_xterm

    builtin_iris-ansi

    builtin_dumb defaulting to 'ansi'

Other than editing each remote .bashrc (similarly to this suggestion), is there any way to set the TERM correctly and automatically on the remote host?

edited Mar 20 '17 at 10:17

Community♦

asked Jun 2 '12 at 20:45

Yoav Aner

3251510

add a comment |

up vote
30
down vote

favorite

I have set up my tmux to use screen-256colors and it works great with vim.

However, when I ssh to a remote host from within tmux, screen-256colors isn't recognized, so I'm getting errors like this:

E558: Terminal entry not found in terminfo 'screen-256color' not known. Available builtin terminals are:

    builtin_ansi

    builtin_xterm

    builtin_iris-ansi

    builtin_dumb defaulting to 'ansi'

Other than editing each remote .bashrc (similarly to this suggestion), is there any way to set the TERM correctly and automatically on the remote host?

edited Mar 20 '17 at 10:17

Community♦

asked Jun 2 '12 at 20:45

Yoav Aner

3251510

I have set up my tmux to use screen-256colors and it works great with vim.

However, when I ssh to a remote host from within tmux, screen-256colors isn't recognized, so I'm getting errors like this:

E558: Terminal entry not found in terminfo 'screen-256color' not known. Available builtin terminals are:

    builtin_ansi

    builtin_xterm

    builtin_iris-ansi

    builtin_dumb defaulting to 'ansi'

Other than editing each remote .bashrc (similarly to this suggestion), is there any way to set the TERM correctly and automatically on the remote host?

ssh terminal colors tmux

edited Mar 20 '17 at 10:17

Community♦

asked Jun 2 '12 at 20:45

Yoav Aner

3251510

edited Mar 20 '17 at 10:17

Community♦

asked Jun 2 '12 at 20:45

Yoav Aner

3251510

edited Mar 20 '17 at 10:17

Community♦

edited Mar 20 '17 at 10:17

Community♦

edited Mar 20 '17 at 10:17

Community♦

asked Jun 2 '12 at 20:45

Yoav Aner

3251510

asked Jun 2 '12 at 20:45

Yoav Aner

3251510

asked Jun 2 '12 at 20:45

Yoav Aner

3251510

add a comment |

2 Answers
2

active

oldest

votes

up vote
39
down vote

accepted

You can copy the necessary terminfo descriptions to remote hosts.

On the local system, dump the description to text format:

infocmp xterm-256color > xterm-256color.ti

infocmp screen-256color > screen-256color.ti

Copy to the remote host and compile:

tic xterm-256color.ti

tic screen-256color.ti

The descriptions will be stored in ~/.terminfo.

(infocmp and tic are part of the ncurses or ncurses-bin packages in most Linux distributions, as well as most BSDs that use ncurses.)

answered Jun 2 '12 at 20:59

grawity

230k35483542

Thanks for the quick and neat answer! I wish I could +2 this one
– Yoav Aner
Jun 2 '12 at 21:38

Agree. Worked like charm !
– Yordan Georgiev
Mar 11 '14 at 10:09

add a comment |

up vote
7
down vote

I have this in my .bashrc:

alias ssh='TERM=screen ssh'

edited Nov 27 at 20:24

Blackwood

2,70961727

answered Jun 11 '12 at 10:59

Ovidiu C.

711

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f431922%2ftmux-and-screen-256-term-not-supported-on-remote-hosts%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

up vote
39
down vote

accepted

You can copy the necessary terminfo descriptions to remote hosts.

On the local system, dump the description to text format:

infocmp xterm-256color > xterm-256color.ti

infocmp screen-256color > screen-256color.ti

Copy to the remote host and compile:

tic xterm-256color.ti

tic screen-256color.ti

The descriptions will be stored in ~/.terminfo.

(infocmp and tic are part of the ncurses or ncurses-bin packages in most Linux distributions, as well as most BSDs that use ncurses.)

answered Jun 2 '12 at 20:59

grawity

230k35483542

Thanks for the quick and neat answer! I wish I could +2 this one
– Yoav Aner
Jun 2 '12 at 21:38

Agree. Worked like charm !
– Yordan Georgiev
Mar 11 '14 at 10:09

add a comment |

up vote
39
down vote

accepted

You can copy the necessary terminfo descriptions to remote hosts.

On the local system, dump the description to text format:

infocmp xterm-256color > xterm-256color.ti

infocmp screen-256color > screen-256color.ti

Copy to the remote host and compile:

tic xterm-256color.ti

tic screen-256color.ti

The descriptions will be stored in ~/.terminfo.

(infocmp and tic are part of the ncurses or ncurses-bin packages in most Linux distributions, as well as most BSDs that use ncurses.)

answered Jun 2 '12 at 20:59

grawity

230k35483542

Thanks for the quick and neat answer! I wish I could +2 this one
– Yoav Aner
Jun 2 '12 at 21:38

Agree. Worked like charm !
– Yordan Georgiev
Mar 11 '14 at 10:09

add a comment |

up vote
39
down vote

accepted

You can copy the necessary terminfo descriptions to remote hosts.

On the local system, dump the description to text format:

infocmp xterm-256color > xterm-256color.ti

infocmp screen-256color > screen-256color.ti

Copy to the remote host and compile:

tic xterm-256color.ti

tic screen-256color.ti

The descriptions will be stored in ~/.terminfo.

(infocmp and tic are part of the ncurses or ncurses-bin packages in most Linux distributions, as well as most BSDs that use ncurses.)

answered Jun 2 '12 at 20:59

grawity

230k35483542

You can copy the necessary terminfo descriptions to remote hosts.

On the local system, dump the description to text format:

infocmp xterm-256color > xterm-256color.ti

infocmp screen-256color > screen-256color.ti

Copy to the remote host and compile:

tic xterm-256color.ti

tic screen-256color.ti

The descriptions will be stored in ~/.terminfo.

(infocmp and tic are part of the ncurses or ncurses-bin packages in most Linux distributions, as well as most BSDs that use ncurses.)

answered Jun 2 '12 at 20:59

grawity

230k35483542

answered Jun 2 '12 at 20:59

grawity

230k35483542

answered Jun 2 '12 at 20:59

grawity

230k35483542

answered Jun 2 '12 at 20:59

grawity

230k35483542

Thanks for the quick and neat answer! I wish I could +2 this one
– Yoav Aner
Jun 2 '12 at 21:38

Agree. Worked like charm !
– Yordan Georgiev
Mar 11 '14 at 10:09

add a comment |

Thanks for the quick and neat answer! I wish I could +2 this one
– Yoav Aner
Jun 2 '12 at 21:38

Agree. Worked like charm !
– Yordan Georgiev
Mar 11 '14 at 10:09

Thanks for the quick and neat answer! I wish I could +2 this one
– Yoav Aner
Jun 2 '12 at 21:38

Agree. Worked like charm !
– Yordan Georgiev
Mar 11 '14 at 10:09

add a comment |

up vote
7
down vote

I have this in my .bashrc:

alias ssh='TERM=screen ssh'

edited Nov 27 at 20:24

Blackwood

2,70961727

answered Jun 11 '12 at 10:59

Ovidiu C.

711

add a comment |

up vote
7
down vote

I have this in my .bashrc:

alias ssh='TERM=screen ssh'

edited Nov 27 at 20:24

Blackwood

2,70961727

answered Jun 11 '12 at 10:59

Ovidiu C.

711

add a comment |

up vote
7
down vote

I have this in my .bashrc:

alias ssh='TERM=screen ssh'

edited Nov 27 at 20:24

Blackwood

2,70961727

answered Jun 11 '12 at 10:59

Ovidiu C.

711

I have this in my .bashrc:

alias ssh='TERM=screen ssh'

edited Nov 27 at 20:24

Blackwood

2,70961727

answered Jun 11 '12 at 10:59

Ovidiu C.

711

edited Nov 27 at 20:24

Blackwood

2,70961727

edited Nov 27 at 20:24

Blackwood

2,70961727

edited Nov 27 at 20:24

Blackwood

2,70961727

answered Jun 11 '12 at 10:59

Ovidiu C.

711

answered Jun 11 '12 at 10:59

Ovidiu C.

711

answered Jun 11 '12 at 10:59

Ovidiu C.

711

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Super User!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Bdtyktl