blocks|key|5485001|text|找出支持哪个术语：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5485002|ls+/usr/share/terminfo/x|code-block|syntax|javascript|5485003|这将为您提供支持的术语列表，例如|5485004|xterm
xterm-xfree86|5485005|设置环境变量：|5485006|export+TERM=xterm-xfree86|5485007|和运行屏幕：|5485008|TERMINFO='/usr/share/terminfo/'+screen|5485009|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

Find out which TERM is supported:

<pre><code>ls /usr/share/terminfo/x
</code></pre>

this will give you a list of supported TERMs i.e.

<pre><code>xterm
xterm-xfree86
</code></pre>

set the environment variable:

<pre><code>export TERM=xterm-xfree86
</code></pre>

and run screen:

<pre><code>TERMINFO='/usr/share/terminfo/' screen
</code></pre>

blocks|key|5484953|text|在你用来ssh的终端应用程序中，转到preferences+->高级->声明终端为：->+xterm-color+(或者xterm-256+color之外的其他东西)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5484954|这个答案来自对这篇文章的评论，这篇文章有另一个解决方案：http://marcoschuh.de/wp/?p=873|offset|length|5484955|entityMap|0|LINK|mutability|MUTABLE|url|http://marcoschuh.de/wp/?p=873^0|0|S|U|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

In the terminal app you are using to ssh, go to preferences -> advanced -> Declare terminal as: -> xterm-color (or something besides xterm-256color)

This answer was taken from a comment to this post, which has another solution:
<a href="http://marcoschuh.de/wp/?p=873" rel="noreferrer">http://marcoschuh.de/wp/?p=873</a>

blocks|key|5485047|text|以我的Buffalo+Linkstation为例，我是这样解决的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5485048|cd+/lib/terminfo/x
ln+-s+xterm-color+xterm-256color|code-block|syntax|javascript|5485049|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

In case of my Buffalo Linkstation I solved it this way:

<pre><code>cd /lib/terminfo/x
ln -s xterm-color xterm-256color
</code></pre>

blocks|key|1955884|text|远程计算机上缺少与“xterm-256color”匹配的terminfo文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1955885|Screen不知道如何模拟您请求的终端(xterm-256+doesn)，因为它没有描述您正在使用的终端的文件(xterm-256+doesn)。|1955886|您可以更改ENV变量TERM以请求远程计算机所具有的终端仿真。例如：export+TERM=vt220，但这将假设您的遥控器有一个vt220+terminfo文件，并且您不会获得漂亮的颜色，并且您必须做其他乏味的事情才能使其保持不变。更好的..。|1955887|如果您的本地计算机有terminfo文件，但您的远程计算机没有，例如，linux/macos与QNAP/QNAS/busybox/rpi/路由器/调制解调器/+If设备对话，那么...|1955888|您可以将必要的文件复制到其中，并指示您的远程终端将其用于屏幕。例如：|1955889|[local]+$+scp+/lib/terminfo/x/xterm-256color+john@nasbox:xterm-256color
[local]+$+ssh+john@nasbox
[remote]+$+ls
xterm-256color
[remote]+$+TERMINFO='/share/homes/john/xterm-256color'+screen|code-block|syntax|javascript|1955890|在这一点上，屏幕应该可以工作。您的本地计算机可能将terminfo目录放在其他地方(/etc/terminfo/和/usr/share/terminfo/是常见的替代方法；您可能需要四处寻找才能找到自己的目录)。|1955891|要对其进行更永久的设置，请将其移动到主目录中的'.terminfo‘目录中(如果您知道得更好，也可以移到其他地方)。例如：|1955892|[remote]+mkdir+-p+.terminfo/x
[remote]+mv+xterm-256color+.terminfo/x
[nasbox]+screen|1955893|同样的技术也应该适用于其他终端仿真。ENV变量TERM确定它应该尝试模拟哪个终端，同名文件提供了实现这一切的魔术代码。|1955894|entityMap^0|S|8|0|0|A|4|Y|H|0|0|0|0|P|8|16|E|1L|K|0|0|0|N|4|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1B|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1C|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|1D|8|@]|D|@]|E|$Q|R]]|$1|S|3|T|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|1L|8|@]|D|@]|E|$]]|$1|W|3|X|5|P|7|1M|8|@]|D|@]|E|$Q|R]]|$1|Y|3|Z|5|6|7|1N|8|@$9|1O|A|1P|B|C]]|D|@]|E|$]]|$1|10|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]]|11|$]]

You're missing a <code>terminfo</code> file on the remote machine which matches 'xterm-256color'. 

Screen doesn't know how to emulate the terminal you've asked for (xterm-256color) because it doesn't have the file which describes the terminal you're using (xterm-256color). 

You could change the ENV variable <code>TERM</code> to ask for a terminal emulation which the remote machine does have. For example: <code>export TERM=vt220</code>, but that would assume your remote has a vt220 terminfo file, and you wouldn't get pretty colors, and you'd have to do other tedious things to make it stick. Better...

If your local machine has terminfo files but your remote machine doesn't, for example, a linux/macos talking to a QNAP/QNAS/busybox/rpi/router/modem/IOTdevice then...

You can copy the necessary file over to it and instruct your remote terminal to use it for screen. eg:

<pre><code>[local] $ scp /lib/terminfo/x/xterm-256color john@nasbox:xterm-256color
[local] $ ssh john@nasbox
[remote] $ ls
xterm-256color
[remote] $ TERMINFO='/share/homes/john/xterm-256color' screen
</code></pre>

Screen should work at this point. Your local machine might have the <code>terminfo</code> directory someplace else (<code>/etc/terminfo/</code> and <code>/usr/share/terminfo/</code> are common alternatives; you might have to dig around to find yours).

To set it up more permanently move it to a '.terminfo' directory in your home directory (or elsewhere if you know better). eg:

<pre><code>[remote] mkdir -p .terminfo/x
[remote] mv xterm-256color .terminfo/x
[nasbox] screen
</code></pre>

The same technique should apply to other terminal emulations. The ENV variable <code>TERM</code> determines which terminal it should try to emulate and the file of the same name provides the magic codes to make it all happen.

blocks|key|1955754|text|我之前使用默认的Mac+OS+X终端应用程序通过ssh访问我的基于Ubuntu的tmux，发现了您所描述的问题-我的bash和tmux设置为screen-256+found，这个选项甚至不在Mac终端偏好设置的列表中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1955755|我尝试添加以下代码行：|1955756|export+TERM=screen-256color|code-block|syntax|javascript|1955757|作为启动命令，但它被忽略，并在启动时被xterm-color覆盖。|1955758|我还设法将Mac终端的设置更改为screen-256+color，方法是选择Shell+>+Export+Settings，然后编辑它生成的XML文件，找到xterm-color行并将其更改为screen-256+color，然后选择Shell+>+Importing+this+settings+file。然而，在启动终端时，我发现它仍然用xterm-color覆盖了这个设置。|1955759|因此，我承认并下载了iTerm2，它允许我通过在纯文本域中输入更改屏幕-256颜色设置(而不是从有限的下拉菜单中选择)。这立刻就起作用了，甚至不需要关闭和重新打开控制台。|offset|length|1955760|所以总而言之，我推荐使用iTerm2，而不是默认的Mac+Terminal+(它似乎不允许对$TERM进行所需的更改)。|1955761|entityMap|0|LINK|mutability|MUTABLE|url|http://www.iterm2.com/#/section/home^0|0|0|0|0|0|A|6|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|13|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@$O|16|P|17|1|18]]|A|$]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

I've previously used the default Mac OS X Terminal app to access my Ubuntu-based tmux via ssh, and found the problem you described - my bash and tmux is set to screen-256color, an option not even in the list in the Mac Terminal preferences.

I tried adding the line:

<pre><code>export TERM=screen-256color
</code></pre>

as a startup command, but it was ignored and was overridden with xterm-color upon startup.

I also managed to change the settings for the Mac Terminal to screen-256color by choosing Shell > Export Settings, and then editing the XML file it generated, finding the line xterm-color and changing it to screen-256color, then Shell > Importing this settings file. Upon launching the Terminal, however, I found it had still overridden this setting with xterm-color.

So I conceded and downloaded <a href="http://www.iterm2.com/#/section/home" rel="noreferrer">iTerm2</a> which allowed me to change the screen-256color setting by typing it into a plain text field (rather than choosing from a limited pulldown menu). This worked straight away without even having to close and reopen the console.

So in conclusion, I recommend using iTerm2 rather than the default Mac Terminal (which doesn't seem to allow the changes to $TERM you require).

blocks|key|1595148|text|你可以在远程服务器(Debian/Ubuntu)上安装ncurses-term来解决这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1595149|entityMap^0|R|C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

You can install <code>ncurses-term</code> on the remote server (Debian/Ubuntu) to fix the issue.

blocks|key|5484994|text|我可以通过菜单Terminal>Preferences>Settings>Advanced>Emulation声明终端为xterm-color来更改Mac+(10.7.5)终端(v2.2.3,303.2)仿真|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5484995|打开新的终端ssh连接将启用新设置。|5484996|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I was able to change Mac OSX(10.7.5) terminal(v2.2.3, 303.2) emulation from the menu
Terminal>Preferences>Settings>Advanced>Emulation
Declare terminal as xterm-color

Opening a new terminal ssh connection enabled the new setting.

blocks|key|1955696|text|您可能需要在Linux主机上安装一个软件包，该软件包提供以下文件之一：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1955697|/usr/share/terminfo/x/xterm-256color
/lib/terminfo/x/xterm-256color|code-block|syntax|javascript|1955698|例如，在Ubuntu上，这是由ncurses-base包提供的。|offset|length|style|CODE|1955699|entityMap^0|0|0|F|C|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

You probably need to install a package on your Linux host which provides one of the following files:

<pre><code>/usr/share/terminfo/x/xterm-256color
/lib/terminfo/x/xterm-256color
</code></pre>

On Ubuntu, for example, this is provided by the <code>ncurses-base</code> package.

blocks|key|1595165|text|另一种情况，例如从screen内部升级到Debian+Buster。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1595166|Terminfo+xterm-256colour格式已更改，因此screen无法恢复以前的会话。|1595167|您可以使用export+TERM=xterm关闭screen会话，然后重新启动screen。这一次，它将使用正确的terminfo文件，因此它将成功。|1595168|来源：https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901843|1595169|entityMap|0|LINK|mutability|MUTABLE|url|https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901843^0|9|6|0|9|F|W|6|0|5|H|0|3|1K|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|14|8|@]|D|@$9|15|A|16|1|17]]|E|$]]|$1|L|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]]]

An other case, e.g. upgrading to Debian Buster from inside <code>screen</code>.

Terminfo <code>xterm-256colour</code> format changed, so <code>screen</code> cannot restore the previous session.

You may use <code>export TERM=xterm</code> to close screen sessions, and then restart screen. This time it will use the correct terminfo file, and so it will succeed.

Source: <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901843" rel="nofollow noreferrer">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901843</a>

blocks|key|5485138|text|我在完全不同的背景下遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5485139|通过输入infocmp，我得到了一条消息，它无法打开terminfo。但它也通知了它试图获得的路径。我所做的就是使用正确的术语(xterm-256+there+)创建该路径。使用find+*我在另一个目录中找到它，并将其复制到新目录中。|5485140|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had the same problem in a totally different context.
By typing infocmp I got the message that it could not open terminfo. But it also informed the path it was trying to get. What I did was simply creating that path with the right term there (xterm-256color). Using find * I found it in another directory and copied to the new directory.

blocks|key|4066513|text|您只需将/usr/share/terminfo/x/xterm-256color复制到您要连接的服务器。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4066514|entityMap^0|4|10|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

You just need to copy <code>/usr/share/terminfo/x/xterm-256color</code> to the server that you're connecting to.

blocks|key|1955931|text|如果你导出一个变量，不要忘记刷新终端源码...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1955932|source+~/.bashrc或者只是打开一个新的终端。这可能就是为什么原版海报在出口方面有问题的原因。|offset|length|style|CODE|1955933|entityMap^0|0|0|G|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Don't forget to refresh terminal source if you export a variable...

<code>source ~/.bashrc</code>
or just open a new terminal. May be why original poster had trouble with exporting.

When I run 

<pre><code>screen
</code></pre>

on the remote host(running Linux), I obtain the following error:

<pre><code>Cannot find terminfo entry for 'xterm-256color'.
</code></pre>

I am running terminal on Mac OSX Lion to access the remote host. I have googled to find out the solution to this problem and it appears that people suggest doing

<pre><code>export TERM=xterm-color
</code></pre>

which doesn't work for me. 

Please help.

Screen: Cannot find terminfo entry for 'xterm-256color'

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

当我跑的时候screen在远程主机(运行Linux)上，我获得以下错误：Cannot find terminfo entry for 'xterm-256color'.我在Mac OSX Lion上运行终端来访问远程主机。我在谷歌上搜索过这个问题的解决方案，似乎人们建议这样做export TERM=xterm-color这对我不起作用。请帮帮忙。

问屏幕:找不到‘xterm-256 Cannot’的terminfo条目
EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问屏幕:找不到‘xterm-256 Cannot’的terminfo条目EN

回答 12

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问屏幕:找不到‘xterm-256 Cannot’的terminfo条目
EN