infocmp.1m.html 24 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445
  1. <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
  2. <!--
  3. * t
  4. ****************************************************************************
  5. * Copyright (c) 1998-2004,2006 Free Software Foundation, Inc. *
  6. * *
  7. * Permission is hereby granted, free of charge, to any person obtaining a *
  8. * copy of this software and associated documentation files (the *
  9. * "Software"), to deal in the Software without restriction, including *
  10. * without limitation the rights to use, copy, modify, merge, publish, *
  11. * distribute, distribute with modifications, sublicense, and/or sell *
  12. * copies of the Software, and to permit persons to whom the Software is *
  13. * furnished to do so, subject to the following conditions: *
  14. * *
  15. * The above copyright notice and this permission notice shall be included *
  16. * in all copies or substantial portions of the Software. *
  17. * *
  18. * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS *
  19. * OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF *
  20. * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. *
  21. * IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, *
  22. * DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR *
  23. * OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR *
  24. * THE USE OR OTHER DEALINGS IN THE SOFTWARE. *
  25. * *
  26. * Except as contained in this notice, the name(s) of the above copyright *
  27. * holders shall not be used in advertising or otherwise to promote the *
  28. * sale, use or other dealings in this Software without prior written *
  29. * authorization. *
  30. ****************************************************************************
  31. * @Id: infocmp.1m,v 1.44 2006/12/24 18:16:31 tom Exp @
  32. -->
  33. <HTML>
  34. <HEAD>
  35. <TITLE>infocmp 1m</TITLE>
  36. <link rev=made href="mailto:bug-ncurses@gnu.org">
  37. <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  38. </HEAD>
  39. <BODY>
  40. <H1>infocmp 1m</H1>
  41. <HR>
  42. <PRE>
  43. <!-- Manpage converted by man2html 3.0.1 -->
  44. <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG> <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>
  45. </PRE>
  46. <H2>NAME</H2><PRE>
  47. <STRONG>infocmp</STRONG> - compare or print out <EM>terminfo</EM> descriptions
  48. </PRE>
  49. <H2>SYNOPSIS</H2><PRE>
  50. <STRONG>infocmp</STRONG> [<STRONG>-1CEFGILTUVcdegilnpqrtux</STRONG>]
  51. [<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>]
  52. [<STRONG>-w</STRONG> <EM>width</EM>] [<STRONG>-A</STRONG> <EM>directory</EM>] [<STRONG>-B</STRONG> <EM>directory</EM>]
  53. [<EM>termname</EM>...]
  54. </PRE>
  55. <H2>DESCRIPTION</H2><PRE>
  56. <STRONG>infocmp</STRONG> can be used to compare a binary <STRONG>terminfo</STRONG> entry
  57. with other terminfo entries, rewrite a <STRONG>terminfo</STRONG> descrip-
  58. tion to take advantage of the <STRONG>use=</STRONG> terminfo field, or
  59. print out a <STRONG>terminfo</STRONG> description from the binary file
  60. (<STRONG>term</STRONG>) in a variety of formats. In all cases, the boolean
  61. fields will be printed first, followed by the numeric
  62. fields, followed by the string fields.
  63. <STRONG>Default</STRONG> <STRONG>Options</STRONG>
  64. If no options are specified and zero or one <EM>termnames</EM> are
  65. specified, the <STRONG>-I</STRONG> option will be assumed. If more than
  66. one <EM>termname</EM> is specified, the <STRONG>-d</STRONG> option will be assumed.
  67. <STRONG>Comparison</STRONG> <STRONG>Options</STRONG> <STRONG>[-d]</STRONG> <STRONG>[-c]</STRONG> <STRONG>[-n]</STRONG>
  68. <STRONG>infocmp</STRONG> compares the <STRONG>terminfo</STRONG> description of the first
  69. terminal <EM>termname</EM> with each of the descriptions given by
  70. the entries for the other terminal's <EM>termnames</EM>. If a
  71. capability is defined for only one of the terminals, the
  72. value returned will depend on the type of the capability:
  73. <STRONG>F</STRONG> for boolean variables, <STRONG>-1</STRONG> for integer variables, and
  74. <STRONG>NULL</STRONG> for string variables.
  75. The <STRONG>-d</STRONG> option produces a list of each capability that is
  76. different between two entries. This option is useful to
  77. show the difference between two entries, created by dif-
  78. ferent people, for the same or similar terminals.
  79. The <STRONG>-c</STRONG> option produces a list of each capability that is
  80. common between two entries. Capabilities that are not set
  81. are ignored. This option can be used as a quick check to
  82. see if the <STRONG>-u</STRONG> option is worth using.
  83. The <STRONG>-n</STRONG> option produces a list of each capability that is
  84. in neither entry. If no <EM>termnames</EM> are given, the environ-
  85. ment variable <STRONG>TERM</STRONG> will be used for both of the <EM>termnames</EM>.
  86. This can be used as a quick check to see if anything was
  87. left out of a description.
  88. <STRONG>Source</STRONG> <STRONG>Listing</STRONG> <STRONG>Options</STRONG> <STRONG>[-I]</STRONG> <STRONG>[-L]</STRONG> <STRONG>[-C]</STRONG> <STRONG>[-r]</STRONG>
  89. The <STRONG>-I</STRONG>, <STRONG>-L</STRONG>, and <STRONG>-C</STRONG> options will produce a source listing
  90. for each terminal named.
  91. <STRONG>-I</STRONG> use the <STRONG>terminfo</STRONG> names
  92. <STRONG>-L</STRONG> use the long C variable name listed in &lt;<STRONG>term.h</STRONG>&gt;
  93. <STRONG>-C</STRONG> use the <STRONG>termcap</STRONG> names
  94. <STRONG>-r</STRONG> when using <STRONG>-C</STRONG>, put out all capabilities in <STRONG>termcap</STRONG> form
  95. If no <EM>termnames</EM> are given, the environment variable <STRONG>TERM</STRONG>
  96. will be used for the terminal name.
  97. The source produced by the <STRONG>-C</STRONG> option may be used directly
  98. as a <STRONG>termcap</STRONG> entry, but not all parameterized strings can
  99. be changed to the <STRONG>termcap</STRONG> format. <STRONG>infocmp</STRONG> will attempt to
  100. convert most of the parameterized information, and any-
  101. thing not converted will be plainly marked in the output
  102. and commented out. These should be edited by hand.
  103. All padding information for strings will be collected
  104. together and placed at the beginning of the string where
  105. <STRONG>termcap</STRONG> expects it. Mandatory padding (padding informa-
  106. tion with a trailing '/') will become optional.
  107. All <STRONG>termcap</STRONG> variables no longer supported by <STRONG>terminfo</STRONG>, but
  108. which are derivable from other <STRONG>terminfo</STRONG> variables, will be
  109. output. Not all <STRONG>terminfo</STRONG> capabilities will be translated;
  110. only those variables which were part of <STRONG>termcap</STRONG> will nor-
  111. mally be output. Specifying the <STRONG>-r</STRONG> option will take off
  112. this restriction, allowing all capabilities to be output
  113. in <EM>termcap</EM> form.
  114. Note that because padding is collected to the beginning of
  115. the capability, not all capabilities are output. Manda-
  116. tory padding is not supported. Because <STRONG>termcap</STRONG> strings
  117. are not as flexible, it is not always possible to convert
  118. a <STRONG>terminfo</STRONG> string capability into an equivalent <STRONG>termcap</STRONG>
  119. format. A subsequent conversion of the <STRONG>termcap</STRONG> file back
  120. into <STRONG>terminfo</STRONG> format will not necessarily reproduce the
  121. original <STRONG>terminfo</STRONG> source.
  122. Some common <STRONG>terminfo</STRONG> parameter sequences, their <STRONG>termcap</STRONG>
  123. equivalents, and some terminal types which commonly have
  124. such sequences, are:
  125. <STRONG>terminfo</STRONG> <STRONG>termcap</STRONG> Representative Terminals
  126. ---------------------------------------------------------------
  127. <STRONG>%p1%c</STRONG> <STRONG>%.</STRONG> adm
  128. <STRONG>%p1%d</STRONG> <STRONG>%d</STRONG> hp, ANSI standard, vt100
  129. <STRONG>%p1%'x'%+%c</STRONG> <STRONG>%+x</STRONG> concept
  130. <STRONG>%i</STRONG> <STRONG>%i</STRONG>q ANSI standard, vt100
  131. <STRONG>%p1%?%'x'%&gt;%t%p1%'y'%+%;</STRONG> <STRONG>%&gt;xy</STRONG> concept
  132. <STRONG>%p2</STRONG> is printed before <STRONG>%p1</STRONG> <STRONG>%r</STRONG> hp
  133. <STRONG>Use=</STRONG> <STRONG>Option</STRONG> <STRONG>[-u]</STRONG>
  134. The <STRONG>-u</STRONG> option produces a <STRONG>terminfo</STRONG> source description of
  135. the first terminal <EM>termname</EM> which is relative to the sum
  136. of the descriptions given by the entries for the other
  137. terminals <EM>termnames</EM>. It does this by analyzing the dif-
  138. ferences between the first <EM>termname</EM> and the other
  139. <EM>termnames</EM> and producing a description with <STRONG>use=</STRONG> fields for
  140. the other terminals. In this manner, it is possible to
  141. retrofit generic terminfo entries into a terminal's
  142. description. Or, if two similar terminals exist, but were
  143. coded at different times or by different people so that
  144. each description is a full description, using <STRONG>infocmp</STRONG> will
  145. show what can be done to change one description to be rel-
  146. ative to the other.
  147. A capability will get printed with an at-sign (@) if it no
  148. longer exists in the first <EM>termname</EM>, but one of the other
  149. <EM>termname</EM> entries contains a value for it. A capability's
  150. value gets printed if the value in the first <EM>termname</EM> is
  151. not found in any of the other <EM>termname</EM> entries, or if the
  152. first of the other <EM>termname</EM> entries that has this capabil-
  153. ity gives a different value for the capability than that
  154. in the first <EM>termname</EM>.
  155. The order of the other <EM>termname</EM> entries is significant.
  156. Since the terminfo compiler <STRONG>tic</STRONG> does a left-to-right scan
  157. of the capabilities, specifying two <STRONG>use=</STRONG> entries that con-
  158. tain differing entries for the same capabilities will pro-
  159. duce different results depending on the order that the
  160. entries are given in. <STRONG>infocmp</STRONG> will flag any such incon-
  161. sistencies between the other <EM>termname</EM> entries as they are
  162. found.
  163. Alternatively, specifying a capability <EM>after</EM> a <STRONG>use=</STRONG> entry
  164. that contains that capability will cause the second speci-
  165. fication to be ignored. Using <STRONG>infocmp</STRONG> to recreate a
  166. description can be a useful check to make sure that every-
  167. thing was specified correctly in the original source
  168. description.
  169. Another error that does not cause incorrect compiled
  170. files, but will slow down the compilation time, is speci-
  171. fying extra <STRONG>use=</STRONG> fields that are superfluous. <STRONG>infocmp</STRONG>
  172. will flag any other <EM>termname</EM> <EM>use=</EM> fields that were not
  173. needed.
  174. <STRONG>Changing</STRONG> <STRONG>Databases</STRONG> <STRONG>[-A</STRONG> <EM>directory</EM>] [-B <EM>directory</EM>]
  175. The location of the compiled <STRONG>terminfo</STRONG> database is taken
  176. from the environment variable <STRONG>TERMINFO</STRONG> . If the variable
  177. is not defined, or the terminal is not found in that loca-
  178. tion, the system <STRONG>terminfo</STRONG> database, in <STRONG>/usr/share/ter-</STRONG>
  179. <STRONG>minfo</STRONG>, will be used. The options <STRONG>-A</STRONG> and <STRONG>-B</STRONG> may be used to
  180. override this location. The <STRONG>-A</STRONG> option will set <STRONG>TERMINFO</STRONG>
  181. for the first <EM>termname</EM> and the <STRONG>-B</STRONG> option will set <STRONG>TERMINFO</STRONG>
  182. for the other <EM>termnames</EM>. With this, it is possible to
  183. compare descriptions for a terminal with the same name
  184. located in two different databases. This is useful for
  185. comparing descriptions for the same terminal created by
  186. different people.
  187. <STRONG>Other</STRONG> <STRONG>Options</STRONG>
  188. <STRONG>-1</STRONG> causes the fields to be printed out one to a line.
  189. Otherwise, the fields will be printed several to a
  190. line to a maximum width of 60 characters.
  191. <STRONG>-a</STRONG> tells <STRONG>infocmp</STRONG> to retain commented-out capabilities
  192. rather than discarding them. Capabilities are com-
  193. mented by prefixing them with a period.
  194. <STRONG>-E</STRONG> Dump the capabilities of the given terminal as
  195. tables, needed in the C initializer for a TERMTYPE
  196. structure (the terminal capability structure in the
  197. <STRONG>&lt;term.h&gt;</STRONG>). This option is useful for preparing ver-
  198. sions of the curses library hardwired for a given
  199. terminal type. The tables are all declared static,
  200. and are named according to the type and the name of
  201. the corresponding terminal entry.
  202. Before ncurses 5.0, the split between the <STRONG>-e</STRONG> and <STRONG>-E</STRONG>
  203. options was not needed; but support for extended
  204. names required making the arrays of terminal capabil-
  205. ities separate from the TERMTYPE structure.
  206. <STRONG>-e</STRONG> Dump the capabilities of the given terminal as a C
  207. initializer for a TERMTYPE structure (the terminal
  208. capability structure in the <STRONG>&lt;term.h&gt;</STRONG>). This option
  209. is useful for preparing versions of the curses
  210. library hardwired for a given terminal type.
  211. <STRONG>-F</STRONG> compare terminfo files. This assumes that two fol-
  212. lowing arguments are filenames. The files are
  213. searched for pairwise matches between entries, with
  214. two entries considered to match if any of their names
  215. do. The report printed to standard output lists
  216. entries with no matches in the other file, and
  217. entries with more than one match. For entries with
  218. exactly one match it includes a difference report.
  219. Normally, to reduce the volume of the report, use
  220. references are not resolved before looking for dif-
  221. ferences, but resolution can be forced by also speci-
  222. fying <STRONG>-r</STRONG>.
  223. <STRONG>-f</STRONG> Display complex terminfo strings which contain
  224. if/then/else/endif expressions indented for readabil-
  225. ity.
  226. <STRONG>-G</STRONG> Display constant literals in decimal form rather than
  227. their character equivalents.
  228. <STRONG>-g</STRONG> Display constant character literals in quoted form
  229. rather than their decimal equivalents.
  230. <STRONG>-i</STRONG> Analyze the initialization (<STRONG>is1</STRONG>, <STRONG>is2</STRONG>, <STRONG>is3</STRONG>), and reset
  231. (<STRONG>rs1</STRONG>, <STRONG>rs2</STRONG>, <STRONG>rs3</STRONG>), strings in the entry. For each
  232. string, the code tries to analyze it into actions in
  233. terms of the other capabilities in the entry, certain
  234. X3.64/ISO 6429/ECMA-48 capabilities, and certain DEC
  235. VT-series private modes (the set of recognized spe-
  236. cial sequences has been selected for completeness
  237. over the existing terminfo database). Each report
  238. line consists of the capability name, followed by a
  239. colon and space, followed by a printable expansion of
  240. the capability string with sections matching recog-
  241. nized actions translated into {}-bracketed descrip-
  242. tions. Here is a list of the DEC/ANSI special
  243. sequences recognized: i.
  244. Action Meaning
  245. -----------------------------------------
  246. RIS full reset
  247. SC save cursor
  248. RC restore cursor
  249. LL home-down
  250. RSR reset scroll region
  251. -----------------------------------------
  252. DECSTR soft reset (VT320)
  253. S7C1T 7-bit controls (VT220)
  254. -----------------------------------------
  255. ISO DEC G0 enable DEC graphics for G0
  256. ISO UK G0 enable UK chars for G0
  257. ISO US G0 enable US chars for G0
  258. ISO DEC G1 enable DEC graphics for G1
  259. ISO UK G1 enable UK chars for G1
  260. ISO US G1 enable US chars for G1
  261. -----------------------------------------
  262. DECPAM application keypad mode
  263. DECPNM normal keypad mode
  264. DECANSI enter ANSI mode
  265. -----------------------------------------
  266. ECMA[+-]AM keyboard action mode
  267. ECMA[+-]IRM insert replace mode
  268. ECMA[+-]SRM send receive mode
  269. ECMA[+-]LNM linefeed mode
  270. -----------------------------------------
  271. DEC[+-]CKM application cursor keys
  272. DEC[+-]ANM set VT52 mode
  273. DEC[+-]COLM 132-column mode
  274. DEC[+-]SCLM smooth scroll
  275. DEC[+-]SCNM reverse video mode
  276. DEC[+-]OM origin mode
  277. DEC[+-]AWM wraparound mode
  278. DEC[+-]ARM auto-repeat mode
  279. It also recognizes a SGR action corresponding to
  280. ANSI/ISO 6429/ECMA Set Graphics Rendition, with the
  281. values NORMAL, BOLD, UNDERLINE, BLINK, and REVERSE.
  282. All but NORMAL may be prefixed with `+' (turn on) or
  283. `-' (turn off).
  284. An SGR0 designates an empty highlight sequence (equivalent
  285. to {SGR:NORMAL}).
  286. <STRONG>-l</STRONG> Set output format to terminfo.
  287. <STRONG>-p</STRONG> Ignore padding specifications when comparing strings.
  288. <STRONG>-q</STRONG> Make the comparison listing shorter by omitting sub-
  289. headings, and using "-" for absent capabilities, "@"
  290. for canceled rather than "NULL".
  291. <STRONG>-R</STRONG><EM>subset</EM>
  292. Restrict output to a given subset. This option is
  293. for use with archaic versions of terminfo like those
  294. on SVr1, Ultrix, or HP/UX that do not support the
  295. full set of SVR4/XSI Curses terminfo; and variants
  296. such as AIX that have their own extensions incompati-
  297. ble with SVr4/XSI. Available terminfo subsets are
  298. "SVr1", "Ultrix", "HP", and "AIX"; see <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>
  299. for details. You can also choose the subset "BSD"
  300. which selects only capabilities with termcap equiva-
  301. lents recognized by 4.4BSD.
  302. <STRONG>-s</STRONG> <EM>[d|i|l|c]</EM>
  303. The <STRONG>-s</STRONG> option sorts the fields within each type
  304. according to the argument below:
  305. <STRONG>d</STRONG> leave fields in the order that they are stored
  306. in the <EM>terminfo</EM> database.
  307. <STRONG>i</STRONG> sort by <EM>terminfo</EM> name.
  308. <STRONG>l</STRONG> sort by the long C variable name.
  309. <STRONG>c</STRONG> sort by the <EM>termcap</EM> name.
  310. If the <STRONG>-s</STRONG> option is not given, the fields printed out
  311. will be sorted alphabetically by the <STRONG>terminfo</STRONG> name
  312. within each type, except in the case of the <STRONG>-C</STRONG> or the
  313. <STRONG>-L</STRONG> options, which cause the sorting to be done by the
  314. <STRONG>termcap</STRONG> name or the long C variable name, respec-
  315. tively.
  316. <STRONG>-T</STRONG> eliminates size-restrictions on the generated text.
  317. This is mainly useful for testing and analysis, since
  318. the compiled descriptions are limited (e.g., 1023 for
  319. termcap, 4096 for terminfo).
  320. <STRONG>-t</STRONG> tells <STRONG>tic</STRONG> to discard commented-out capabilities.
  321. Normally when translating from terminfo to termcap,
  322. untranslatable capabilities are commented-out.
  323. <STRONG>-U</STRONG> tells <STRONG>infocmp</STRONG> to not post-process the data after
  324. parsing the source file. This feature helps when
  325. comparing the actual contents of two source files,
  326. since it excludes the inferences that <STRONG>infocmp</STRONG> makes
  327. to fill in missing data.
  328. <STRONG>-V</STRONG> reports the version of ncurses which was used in this
  329. program, and exits.
  330. <STRONG>-v</STRONG> <EM>n</EM> prints out tracing information on standard error as
  331. the program runs. Higher values of n induce greater
  332. verbosity.
  333. <STRONG>-w</STRONG> <EM>width</EM>
  334. changes the output to <EM>width</EM> characters.
  335. <STRONG>-x</STRONG> print information for user-defined capabilities.
  336. These are extensions to the terminfo repertoire which
  337. can be loaded using the <STRONG>-x</STRONG> option of <STRONG>tic</STRONG>.
  338. </PRE>
  339. <H2>FILES</H2><PRE>
  340. /usr/share/terminfo Compiled terminal description
  341. database.
  342. </PRE>
  343. <H2>EXTENSIONS</H2><PRE>
  344. The <STRONG>-E</STRONG>, <STRONG>-F</STRONG>, <STRONG>-G</STRONG>, <STRONG>-R</STRONG>, <STRONG>-T</STRONG>, <STRONG>-V</STRONG>, <STRONG>-a</STRONG>, <STRONG>-e</STRONG>, <STRONG>-f</STRONG>, <STRONG>-g</STRONG>, <STRONG>-i</STRONG>, <STRONG>-l</STRONG>, <STRONG>-p</STRONG>, <STRONG>-q</STRONG>
  345. and <STRONG>-t</STRONG> options are not supported in SVr4 curses.
  346. The <STRONG>-r</STRONG> option's notion of `termcap' capabilities is System
  347. V Release 4's. Actual BSD curses versions will have a
  348. more restricted set. To see only the 4.4BSD set, use <STRONG>-r</STRONG>
  349. <STRONG>-RBSD</STRONG>.
  350. </PRE>
  351. <H2>BUGS</H2><PRE>
  352. The <STRONG>-F</STRONG> option of <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG> should be a <STRONG><A HREF="toe.1m.html">toe(1m)</A></STRONG> mode.
  353. </PRE>
  354. <H2>SEE ALSO</H2><PRE>
  355. <STRONG><A HREF="captoinfo.1m.html">captoinfo(1m)</A></STRONG>, <STRONG><A HREF="infotocap.1m.html">infotocap(1m)</A></STRONG>, <STRONG><A HREF="tic.1m.html">tic(1m)</A></STRONG>, <STRONG><A HREF="toe.1m.html">toe(1m)</A></STRONG>,
  356. <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>.
  357. This describes <STRONG>ncurses</STRONG> version 5.6 (patch 20081011).
  358. </PRE>
  359. <H2>AUTHOR</H2><PRE>
  360. Eric S. Raymond &lt;esr@snark.thyrsus.com&gt; and
  361. Thomas E. Dickey &lt;dickey@invisible-island.net&gt;
  362. <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>
  363. </PRE>
  364. <HR>
  365. <ADDRESS>
  366. Man(1) output converted with
  367. <a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
  368. </ADDRESS>
  369. </BODY>
  370. </HTML>