Tmux under Kitty terminal
I recently discovered the neat kitty as some aspects of the themes I'm using under ZSH don't render quite right under Xfce Terminal but do under kitty.
Unfortunately I've hit a snag when it comes to using tmux on SSH connections, if SSH from my desktop/server (running Gentoo) to any of my Raspberry Pis (running Arch Linux ARM) or my VPS (also running Arch Linux) and start a Tmux session I'm informed....
open terminal failed: missing or unsuitable terminal: xterm-kitty
However, I've a laptop which is also running Arch and if I SSH to it from my desktop/server and start an SSH session there are no problems, and vice versa, SSHing from laptop to desktop/server and Tmux runs fine.
I should add that I can run Tmux sessions when SSHing to the Raspberry Pis/VPS's that are running Arch Linux if its under an Xfce Terminal.
Any ideas as to how I can investigate or solve this such that Tmux sessions work everywhere?
ssh tmux kitty
edited 10 mins ago
Evan Carroll
5,596114481
asked Sep 22 '18 at 8:03
slacklineslackline
2111412
add a comment |
I recently discovered the neat kitty as some aspects of the themes I'm using under ZSH don't render quite right under Xfce Terminal but do under kitty.
Unfortunately I've hit a snag when it comes to using tmux on SSH connections, if SSH from my desktop/server (running Gentoo) to any of my Raspberry Pis (running Arch Linux ARM) or my VPS (also running Arch Linux) and start a Tmux session I'm informed....
open terminal failed: missing or unsuitable terminal: xterm-kitty
However, I've a laptop which is also running Arch and if I SSH to it from my desktop/server and start an SSH session there are no problems, and vice versa, SSHing from laptop to desktop/server and Tmux runs fine.
I should add that I can run Tmux sessions when SSHing to the Raspberry Pis/VPS's that are running Arch Linux if its under an Xfce Terminal.
Any ideas as to how I can investigate or solve this such that Tmux sessions work everywhere?
ssh tmux kitty
edited 10 mins ago
Evan Carroll
5,596114481
asked Sep 22 '18 at 8:03
slacklineslackline
2111412
add a comment |
I recently discovered the neat kitty as some aspects of the themes I'm using under ZSH don't render quite right under Xfce Terminal but do under kitty.
Unfortunately I've hit a snag when it comes to using tmux on SSH connections, if SSH from my desktop/server (running Gentoo) to any of my Raspberry Pis (running Arch Linux ARM) or my VPS (also running Arch Linux) and start a Tmux session I'm informed....
open terminal failed: missing or unsuitable terminal: xterm-kitty
However, I've a laptop which is also running Arch and if I SSH to it from my desktop/server and start an SSH session there are no problems, and vice versa, SSHing from laptop to desktop/server and Tmux runs fine.
I should add that I can run Tmux sessions when SSHing to the Raspberry Pis/VPS's that are running Arch Linux if its under an Xfce Terminal.
Any ideas as to how I can investigate or solve this such that Tmux sessions work everywhere?
ssh tmux kitty
edited 10 mins ago
Evan Carroll
5,596114481
asked Sep 22 '18 at 8:03
slacklineslackline
2111412
I recently discovered the neat kitty as some aspects of the themes I'm using under ZSH don't render quite right under Xfce Terminal but do under kitty.
Unfortunately I've hit a snag when it comes to using tmux on SSH connections, if SSH from my desktop/server (running Gentoo) to any of my Raspberry Pis (running Arch Linux ARM) or my VPS (also running Arch Linux) and start a Tmux session I'm informed....
open terminal failed: missing or unsuitable terminal: xterm-kitty
However, I've a laptop which is also running Arch and if I SSH to it from my desktop/server and start an SSH session there are no problems, and vice versa, SSHing from laptop to desktop/server and Tmux runs fine.
I should add that I can run Tmux sessions when SSHing to the Raspberry Pis/VPS's that are running Arch Linux if its under an Xfce Terminal.
Any ideas as to how I can investigate or solve this such that Tmux sessions work everywhere?
ssh tmux kitty
ssh tmux kitty
edited 10 mins ago
Evan Carroll
5,596114481
asked Sep 22 '18 at 8:03
slacklineslackline
2111412
edited 10 mins ago
Evan Carroll
5,596114481
asked Sep 22 '18 at 8:03
slacklineslackline
2111412
edited 10 mins ago
Evan Carroll
5,596114481
edited 10 mins ago
Evan Carroll
5,596114481
edited 10 mins ago
Evan Carroll
5,596114481
5,596114481
asked Sep 22 '18 at 8:03
slacklineslackline
2111412
asked Sep 22 '18 at 8:03
slacklineslackline
2111412
asked Sep 22 '18 at 8:03
slacklineslackline
2111412
2111412
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
If you receive error messages such as "Terminal unknown, missing or unsuitable terminal" upon logging in, this means the server does not recognize your terminal.
The correct solution is to install the client terminal's terminfo file on the server. This tells console programs on the server how to correctly interact with your terminal. You can get info about current terminfo using infocmp and then find out which package owns it.
If you cannot install it normally, you can copy your terminfo to your home directory on the server:
$ ssh myserver mkdir -p ~/.terminfo/${TERM:0:1}
$ scp /usr/share/terminfo/${TERM:0:1}/$TERM myserver:~/.terminfo/${TERM:0:1}/
After logging in and out from the server the problem should be fixed.
1
Brilliant, thank your for the clear and succinct explanation and solution. To ease maintenance I opted to install kitty on the remote servers that didn't already have it installed, although I if I ever need to save space I'll adopt the/.terminfomirroring and add it to my dotfiles.
– slackline
Sep 22 '18 at 11:05
add a comment |
If you're connected to a machine where it's not possible to install terminfo files, you can set the TERM environment variable to to something that is supported by the machine — profiles that are pretty much compatible with kitty, in decreasing order of preference, include
- xterm-256color
- xterm-color
- xterm
- vt102
If you want the login shell (e.g. bash) on the remote machine to pick up the correct terminal, you should export it into the environment before running ssh. If you don't care because you're only going to run tmux, you can set it after. Naturally, you will lose some of the cool features of kitty, but in a case where you can't install terminfo and having the basic features takes preference, it can still be handy.
answered Sep 22 '18 at 14:07
hobbshobbs
42339
This is an error called out in the XTerm FAQ. One should not just blithely go around using thexterm-*entries with things that are not XTerm, and thevt102entry describes an actual DEC VT 102 which almost all terminal emulators do not in fact emulate. The very premise of this answer is wrong, too. The questioner can install terminfo files, because terminfo (as built on Arch) also looks in one's home directory.
– JdeBP
Sep 22 '18 at 15:00
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f470676%2ftmux-under-kitty-terminal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you receive error messages such as "Terminal unknown, missing or unsuitable terminal" upon logging in, this means the server does not recognize your terminal.
The correct solution is to install the client terminal's terminfo file on the server. This tells console programs on the server how to correctly interact with your terminal. You can get info about current terminfo using infocmp and then find out which package owns it.
If you cannot install it normally, you can copy your terminfo to your home directory on the server:
$ ssh myserver mkdir -p ~/.terminfo/${TERM:0:1}
$ scp /usr/share/terminfo/${TERM:0:1}/$TERM myserver:~/.terminfo/${TERM:0:1}/
After logging in and out from the server the problem should be fixed.
1
Brilliant, thank your for the clear and succinct explanation and solution. To ease maintenance I opted to install kitty on the remote servers that didn't already have it installed, although I if I ever need to save space I'll adopt the/.terminfomirroring and add it to my dotfiles.
– slackline
Sep 22 '18 at 11:05
add a comment |
If you receive error messages such as "Terminal unknown, missing or unsuitable terminal" upon logging in, this means the server does not recognize your terminal.
The correct solution is to install the client terminal's terminfo file on the server. This tells console programs on the server how to correctly interact with your terminal. You can get info about current terminfo using infocmp and then find out which package owns it.
If you cannot install it normally, you can copy your terminfo to your home directory on the server:
$ ssh myserver mkdir -p ~/.terminfo/${TERM:0:1}
$ scp /usr/share/terminfo/${TERM:0:1}/$TERM myserver:~/.terminfo/${TERM:0:1}/
After logging in and out from the server the problem should be fixed.
1
Brilliant, thank your for the clear and succinct explanation and solution. To ease maintenance I opted to install kitty on the remote servers that didn't already have it installed, although I if I ever need to save space I'll adopt the/.terminfomirroring and add it to my dotfiles.
– slackline
Sep 22 '18 at 11:05
add a comment |
If you receive error messages such as "Terminal unknown, missing or unsuitable terminal" upon logging in, this means the server does not recognize your terminal.
The correct solution is to install the client terminal's terminfo file on the server. This tells console programs on the server how to correctly interact with your terminal. You can get info about current terminfo using infocmp and then find out which package owns it.
If you cannot install it normally, you can copy your terminfo to your home directory on the server:
$ ssh myserver mkdir -p ~/.terminfo/${TERM:0:1}
$ scp /usr/share/terminfo/${TERM:0:1}/$TERM myserver:~/.terminfo/${TERM:0:1}/
After logging in and out from the server the problem should be fixed.
If you receive error messages such as "Terminal unknown, missing or unsuitable terminal" upon logging in, this means the server does not recognize your terminal.
The correct solution is to install the client terminal's terminfo file on the server. This tells console programs on the server how to correctly interact with your terminal. You can get info about current terminfo using infocmp and then find out which package owns it.
If you cannot install it normally, you can copy your terminfo to your home directory on the server:
$ ssh myserver mkdir -p ~/.terminfo/${TERM:0:1}
$ scp /usr/share/terminfo/${TERM:0:1}/$TERM myserver:~/.terminfo/${TERM:0:1}/
After logging in and out from the server the problem should be fixed.
edited Sep 22 '18 at 12:32
answered Sep 22 '18 at 9:09
user88036
1
Brilliant, thank your for the clear and succinct explanation and solution. To ease maintenance I opted to install kitty on the remote servers that didn't already have it installed, although I if I ever need to save space I'll adopt the/.terminfomirroring and add it to my dotfiles.
– slackline
Sep 22 '18 at 11:05
add a comment |
1
Brilliant, thank your for the clear and succinct explanation and solution. To ease maintenance I opted to install kitty on the remote servers that didn't already have it installed, although I if I ever need to save space I'll adopt the/.terminfomirroring and add it to my dotfiles.
– slackline
Sep 22 '18 at 11:05
1
1
Brilliant, thank your for the clear and succinct explanation and solution. To ease maintenance I opted to install kitty on the remote servers that didn't already have it installed, although I if I ever need to save space I'll adopt the
/.terminfo mirroring and add it to my dotfiles.– slackline
Sep 22 '18 at 11:05
Brilliant, thank your for the clear and succinct explanation and solution. To ease maintenance I opted to install kitty on the remote servers that didn't already have it installed, although I if I ever need to save space I'll adopt the
/.terminfo mirroring and add it to my dotfiles.– slackline
Sep 22 '18 at 11:05
add a comment |
If you're connected to a machine where it's not possible to install terminfo files, you can set the TERM environment variable to to something that is supported by the machine — profiles that are pretty much compatible with kitty, in decreasing order of preference, include
- xterm-256color
- xterm-color
- xterm
- vt102
If you want the login shell (e.g. bash) on the remote machine to pick up the correct terminal, you should export it into the environment before running ssh. If you don't care because you're only going to run tmux, you can set it after. Naturally, you will lose some of the cool features of kitty, but in a case where you can't install terminfo and having the basic features takes preference, it can still be handy.
answered Sep 22 '18 at 14:07
hobbshobbs
42339
This is an error called out in the XTerm FAQ. One should not just blithely go around using thexterm-*entries with things that are not XTerm, and thevt102entry describes an actual DEC VT 102 which almost all terminal emulators do not in fact emulate. The very premise of this answer is wrong, too. The questioner can install terminfo files, because terminfo (as built on Arch) also looks in one's home directory.
– JdeBP
Sep 22 '18 at 15:00
add a comment |
If you're connected to a machine where it's not possible to install terminfo files, you can set the TERM environment variable to to something that is supported by the machine — profiles that are pretty much compatible with kitty, in decreasing order of preference, include
- xterm-256color
- xterm-color
- xterm
- vt102
If you want the login shell (e.g. bash) on the remote machine to pick up the correct terminal, you should export it into the environment before running ssh. If you don't care because you're only going to run tmux, you can set it after. Naturally, you will lose some of the cool features of kitty, but in a case where you can't install terminfo and having the basic features takes preference, it can still be handy.
answered Sep 22 '18 at 14:07
hobbshobbs
42339
This is an error called out in the XTerm FAQ. One should not just blithely go around using thexterm-*entries with things that are not XTerm, and thevt102entry describes an actual DEC VT 102 which almost all terminal emulators do not in fact emulate. The very premise of this answer is wrong, too. The questioner can install terminfo files, because terminfo (as built on Arch) also looks in one's home directory.
– JdeBP
Sep 22 '18 at 15:00
add a comment |
If you're connected to a machine where it's not possible to install terminfo files, you can set the TERM environment variable to to something that is supported by the machine — profiles that are pretty much compatible with kitty, in decreasing order of preference, include
- xterm-256color
- xterm-color
- xterm
- vt102
If you want the login shell (e.g. bash) on the remote machine to pick up the correct terminal, you should export it into the environment before running ssh. If you don't care because you're only going to run tmux, you can set it after. Naturally, you will lose some of the cool features of kitty, but in a case where you can't install terminfo and having the basic features takes preference, it can still be handy.
answered Sep 22 '18 at 14:07
hobbshobbs
42339
If you're connected to a machine where it's not possible to install terminfo files, you can set the TERM environment variable to to something that is supported by the machine — profiles that are pretty much compatible with kitty, in decreasing order of preference, include
- xterm-256color
- xterm-color
- xterm
- vt102
If you want the login shell (e.g. bash) on the remote machine to pick up the correct terminal, you should export it into the environment before running ssh. If you don't care because you're only going to run tmux, you can set it after. Naturally, you will lose some of the cool features of kitty, but in a case where you can't install terminfo and having the basic features takes preference, it can still be handy.
answered Sep 22 '18 at 14:07
hobbshobbs
42339
answered Sep 22 '18 at 14:07
hobbshobbs
42339
answered Sep 22 '18 at 14:07
hobbshobbs
42339
answered Sep 22 '18 at 14:07
hobbshobbs
42339
42339
This is an error called out in the XTerm FAQ. One should not just blithely go around using thexterm-*entries with things that are not XTerm, and thevt102entry describes an actual DEC VT 102 which almost all terminal emulators do not in fact emulate. The very premise of this answer is wrong, too. The questioner can install terminfo files, because terminfo (as built on Arch) also looks in one's home directory.
– JdeBP
Sep 22 '18 at 15:00
add a comment |
This is an error called out in the XTerm FAQ. One should not just blithely go around using thexterm-*entries with things that are not XTerm, and thevt102entry describes an actual DEC VT 102 which almost all terminal emulators do not in fact emulate. The very premise of this answer is wrong, too. The questioner can install terminfo files, because terminfo (as built on Arch) also looks in one's home directory.
– JdeBP
Sep 22 '18 at 15:00
This is an error called out in the XTerm FAQ. One should not just blithely go around using the
xterm-* entries with things that are not XTerm, and the vt102 entry describes an actual DEC VT 102 which almost all terminal emulators do not in fact emulate. The very premise of this answer is wrong, too. The questioner can install terminfo files, because terminfo (as built on Arch) also looks in one's home directory.– JdeBP
Sep 22 '18 at 15:00
This is an error called out in the XTerm FAQ. One should not just blithely go around using the
xterm-* entries with things that are not XTerm, and the vt102 entry describes an actual DEC VT 102 which almost all terminal emulators do not in fact emulate. The very premise of this answer is wrong, too. The questioner can install terminfo files, because terminfo (as built on Arch) also looks in one's home directory.– JdeBP
Sep 22 '18 at 15:00
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f470676%2ftmux-under-kitty-terminal%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
