📄 infocmp.1m.html
字号:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"><!-- * t **************************************************************************** * Copyright (c) 1998-2002,2003 Free Software Foundation, Inc. * * * * Permission is hereby granted, free of charge, to any person obtaining a * * copy of this software and associated documentation files (the * * "Software"), to deal in the Software without restriction, including * * without limitation the rights to use, copy, modify, merge, publish, * * distribute, distribute with modifications, sublicense, and/or sell * * copies of the Software, and to permit persons to whom the Software is * * furnished to do so, subject to the following conditions: * * * * The above copyright notice and this permission notice shall be included * * in all copies or substantial portions of the Software. * * * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS * * OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF * * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. * * IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, * * DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR * * OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR * * THE USE OR OTHER DEALINGS IN THE SOFTWARE. * * * * Except as contained in this notice, the name(s) of the above copyright * * holders shall not be used in advertising or otherwise to promote the * * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** * @Id: infocmp.1m,v 1.34 2003/10/25 16:19:01 tom Exp @--><HTML><HEAD><TITLE>infocmp 1m</TITLE><link rev=made href="mailto:bug-ncurses@gnu.org"><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></HEAD><BODY><H1>infocmp 1m</H1><HR><PRE><!-- Manpage converted by man2html 3.0.1 --><STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG> <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG></PRE><H2>NAME</H2><PRE> <STRONG>infocmp</STRONG> - compare or print out <EM>terminfo</EM> descriptions</PRE><H2>SYNOPSIS</H2><PRE> <STRONG>infocmp</STRONG> [<STRONG>-1CEFGILTVcdegilnpqrtu</STRONG>] [<STRONG>-v</STRONG> <EM>n</EM>] [<STRONG>-s</STRONG> <STRONG>d</STRONG>| <STRONG>i</STRONG>| <STRONG>l</STRONG>| <STRONG>c</STRONG>] [<STRONG>-R</STRONG> <STRONG>subset</STRONG>] [<STRONG>-w</STRONG> <EM>width</EM>] [<STRONG>-A</STRONG> <EM>directory</EM>] [<STRONG>-B</STRONG> <EM>directory</EM>] [<EM>termname</EM>...]</PRE><H2>DESCRIPTION</H2><PRE> <STRONG>infocmp</STRONG> can be used to compare a binary <STRONG>terminfo</STRONG> entry with other terminfo entries, rewrite a <STRONG>terminfo</STRONG> descrip- tion to take advantage of the <STRONG>use=</STRONG> terminfo field, or print out a <STRONG>terminfo</STRONG> description from the binary file (<STRONG>term</STRONG>) in a variety of formats. In all cases, the boolean fields will be printed first, followed by the numeric fields, followed by the string fields. <STRONG>Default</STRONG> <STRONG>Options</STRONG> If no options are specified and zero or one <EM>termnames</EM> are specified, the <STRONG>-I</STRONG> option will be assumed. If more than one <EM>termname</EM> is specified, the <STRONG>-d</STRONG> option will be assumed. <STRONG>Comparison</STRONG> <STRONG>Options</STRONG> <STRONG>[-d]</STRONG> <STRONG>[-c]</STRONG> <STRONG>[-n]</STRONG> <STRONG>infocmp</STRONG> compares the <STRONG>terminfo</STRONG> description of the first terminal <EM>termname</EM> with each of the descriptions given by the entries for the other terminal's <EM>termnames</EM>. If a capability is defined for only one of the terminals, the value returned will depend on the type of the capability: <STRONG>F</STRONG> for boolean variables, <STRONG>-1</STRONG> for integer variables, and <STRONG>NULL</STRONG> for string variables. The <STRONG>-d</STRONG> option produces a list of each capability that is different between two entries. This option is useful to show the difference between two entries, created by dif- ferent people, for the same or similar terminals. The <STRONG>-c</STRONG> option produces a list of each capability that is common between two entries. Capabilities that are not set are ignored. This option can be used as a quick check to see if the <STRONG>-u</STRONG> option is worth using. The <STRONG>-n</STRONG> option produces a list of each capability that is in neither entry. If no <EM>termnames</EM> are given, the environ- ment variable <STRONG>TERM</STRONG> will be used for both of the <EM>termnames</EM>. This can be used as a quick check to see if anything was left out of a description. <STRONG>Source</STRONG> <STRONG>Listing</STRONG> <STRONG>Options</STRONG> <STRONG>[-I]</STRONG> <STRONG>[-L]</STRONG> <STRONG>[-C]</STRONG> <STRONG>[-r]</STRONG> The <STRONG>-I</STRONG>, <STRONG>-L</STRONG>, and <STRONG>-C</STRONG> options will produce a source listing for each terminal named. <STRONG>-I</STRONG> use the <STRONG>terminfo</STRONG> names <STRONG>-L</STRONG> use the long C variable name listed in <<STRONG>term.h</STRONG>> <STRONG>-C</STRONG> use the <STRONG>termcap</STRONG> names <STRONG>-r</STRONG> when using <STRONG>-C</STRONG>, put out all capabilities in <STRONG>termcap</STRONG> form If no <EM>termnames</EM> are given, the environment variable <STRONG>TERM</STRONG> will be used for the terminal name. The source produced by the <STRONG>-C</STRONG> option may be used directly as a <STRONG>termcap</STRONG> entry, but not all parameterized strings can be changed to the <STRONG>termcap</STRONG> format. <STRONG>infocmp</STRONG> will attempt to convert most of the parameterized information, and any- thing not converted will be plainly marked in the output and commented out. These should be edited by hand. All padding information for strings will be collected together and placed at the beginning of the string where <STRONG>termcap</STRONG> expects it. Mandatory padding (padding informa- tion with a trailing '/') will become optional. All <STRONG>termcap</STRONG> variables no longer supported by <STRONG>terminfo</STRONG>, but which are derivable from other <STRONG>terminfo</STRONG> variables, will be output. Not all <STRONG>terminfo</STRONG> capabilities will be translated; only those variables which were part of <STRONG>termcap</STRONG> will nor- mally be output. Specifying the <STRONG>-r</STRONG> option will take off this restriction, allowing all capabilities to be output in <EM>termcap</EM> form. Note that because padding is collected to the beginning of the capability, not all capabilities are output. Manda- tory padding is not supported. Because <STRONG>termcap</STRONG> strings are not as flexible, it is not always possible to convert a <STRONG>terminfo</STRONG> string capability into an equivalent <STRONG>termcap</STRONG> format. A subsequent conversion of the <STRONG>termcap</STRONG> file back into <STRONG>terminfo</STRONG> format will not necessarily reproduce the original <STRONG>terminfo</STRONG> source. Some common <STRONG>terminfo</STRONG> parameter sequences, their <STRONG>termcap</STRONG> equivalents, and some terminal types which commonly have such sequences, are: <STRONG>terminfo</STRONG> <STRONG>termcap</STRONG> Representative Terminals --------------------------------------------------------------- <STRONG>%p1%c</STRONG> <STRONG>%.</STRONG> adm <STRONG>%p1%d</STRONG> <STRONG>%d</STRONG> hp, ANSI standard, vt100 <STRONG>%p1%'x'%+%c</STRONG> <STRONG>%+x</STRONG> concept <STRONG>%i</STRONG> <STRONG>%i</STRONG>q ANSI standard, vt100 <STRONG>%p1%?%'x'%>%t%p1%'y'%+%;</STRONG> <STRONG>%>xy</STRONG> concept <STRONG>%p2</STRONG> is printed before <STRONG>%p1</STRONG> <STRONG>%r</STRONG> hp <STRONG>Use=</STRONG> <STRONG>Option</STRONG> <STRONG>[-u]</STRONG> The <STRONG>-u</STRONG> option produces a <STRONG>terminfo</STRONG> source description of the first terminal <EM>termname</EM> which is relative to the sum of the descriptions given by the entries for the other terminals <EM>termnames</EM>. It does this by analyzing the dif- ferences between the first <EM>termname</EM> and the other <EM>termnames</EM> and producing a description with <STRONG>use=</STRONG> fields for the other terminals. In this manner, it is possible to retrofit generic terminfo entries into a terminal's description. Or, if two similar terminals exist, but were coded at different times or by different people so that each description is a full description, using <STRONG>infocmp</STRONG> will show what can be done to change one description to be rel- ative to the other. A capability will get printed with an at-sign (@) if it no longer exists in the first <EM>termname</EM>, but one of the other <EM>termname</EM> entries contains a value for it. A capability's value gets printed if the value in the first <EM>termname</EM> is not found in any of the other <EM>termname</EM> entries, or if the first of the other <EM>termname</EM> entries that has this capabil- ity gives a different value for the capability than that in the first <EM>termname</EM>. The order of the other <EM>termname</EM> entries is significant. Since the terminfo compiler <STRONG>tic</STRONG> does a left-to-right scan of the capabilities, specifying two <STRONG>use=</STRONG> entries that con- tain differing entries for the same capabilities will pro- duce different results depending on the order that the entries are given in. <STRONG>infocmp</STRONG> will flag any such incon- sistencies between the other <EM>termname</EM> entries as they are found. Alternatively, specifying a capability <EM>after</EM> a <STRONG>use=</STRONG> entry that contains that capability will cause the second speci- fication to be ignored. Using <STRONG>infocmp</STRONG> to recreate a description can be a useful check to make sure that every- thing was specified correctly in the original source description. Another error that does not cause incorrect compiled files, but will slow down the compilation time, is speci- fying extra <STRONG>use=</STRONG> fields that are superfluous. <STRONG>infocmp</STRONG> will flag any other <EM>termname</EM> <EM>use=</EM> fields that were not needed. <STRONG>Changing</STRONG> <STRONG>Databases</STRONG> <STRONG>[-A</STRONG> <EM>directory</EM>] [-B <EM>directory</EM>] The location of the compiled <STRONG>terminfo</STRONG> database is taken from the environment variable <STRONG>TERMINFO</STRONG> . If the variable is not defined, or the terminal is not found in that loca- tion, the system <STRONG>terminfo</STRONG> database, in <STRONG>/usr/share/ter-</STRONG> <STRONG>minfo</STRONG>, will be used. The options <STRONG>-A</STRONG> and <STRONG>-B</STRONG> may be used to override this location. The <STRONG>-A</STRONG> option will set <STRONG>TERMINFO</STRONG> for the first <EM>termname</EM> and the <STRONG>-B</STRONG> option will set <STRONG>TERMINFO</STRONG> for the other <EM>termnames</EM>. With this, it is possible to compare descriptions for a terminal with the same name located in two different databases. This is useful for⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -