1 # $XTermId: terminfo,v 1.155 2007/11/11 23:26:52 tom Exp $
3 # $XFree86: xc/programs/xterm/terminfo,v 3.59 2006/02/13 01:14:59 dickey Exp $
5 # Updates/notes/new entries (e.g., xterm-8bit, xterm-16color, xterm-256color)
8 #------------------------------------------------------------------------------
9 # Copyright 1996-2006,2007 by Thomas E. Dickey
13 # Permission is hereby granted, free of charge, to any person obtaining a
14 # copy of this software and associated documentation files (the
15 # "Software"), to deal in the Software without restriction, including
16 # without limitation the rights to use, copy, modify, merge, publish,
17 # distribute, sublicense, and/or sell copies of the Software, and to
18 # permit persons to whom the Software is furnished to do so, subject to
19 # the following conditions:
21 # The above copyright notice and this permission notice shall be included
22 # in all copies or substantial portions of the Software.
24 # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
25 # OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
26 # MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
27 # IN NO EVENT SHALL THE ABOVE LISTED COPYRIGHT HOLDER(S) BE LIABLE FOR ANY
28 # CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
29 # TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
30 # SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
32 # Except as contained in this notice, the name(s) of the above copyright
33 # holders shall not be used in advertising or otherwise to promote the
34 # sale, use or other dealings in this Software without prior written
36 #------------------------------------------------------------------------------
38 # Special Capabilities:
39 # --------------------
40 # ich has a corresponding capability that inserts a single blank. We could
41 # have used ich1=\E[@, which works with ncurses, but that is not standard
42 # behavior. If it is set, then SVr4 vi (e.g., Solaris 2.6) emits both
44 # meml locks memory above the cursor; memu unlocks (ala HP terminals). This
45 # is not recognized by some older (e.g., SVr3) tic programs, but none
46 # do more than warn about it. Ignore the warning.
47 # smcup clears memory before switching to the alternate screen. The older
48 # (deprecated) \E[?47h did not do this, requiring applications to
49 # embed a \E[2J in the rmcup string. However, that behavior cannot
50 # be disabled via titeInhibit, making that resource not function as
51 # intended on systems with terminfo.
52 # rs2/is2 are shorter with XFree86 xterm because it supports DECSTR. We
53 # use the shorter sequence for compatibility with the termcap, which
54 # is trimmed to keep it shorter than 1023 characters. It (escape \E[!p)
55 # replaces these in the conventional vt100 reset-string:
56 # \E7 - save cursor (fixes origin-mode side-effect)
57 # \E[r - reset scrolling margins
58 # \E[m - reset SGR (including color)
59 # \E[?7h - reset wraparound mode (DECAWM)
60 # \E[?1l - reset application cursor keys (DECCKM)
61 # \E[?6l - reset origin mode (DECOM)
62 # \E8 - restore cursor
63 # DECSTR is recognized by XFree86 xterm even in vt52 mode.
67 # XFree86 xterm emulates vt220 if the decTerminalID resource is set to 200 or
68 # higher. Otherwise it emulates a vt100 or vt52 depending on the value of the
69 # resource. When emulating a vt220, we support the editing keypad. Sun and PC
70 # keyboards have an editing keypad which is similar to the vt220:
72 # VT220 editing keypad
73 # ----------------------------
76 # ----------------------------
78 # Sun/PC editing keypad
79 # ----------------------------
82 # ----------------------------
84 # If the sunKeyboard resource is true, we map it this way (adjusting the values
85 # of Home, End and Delete):
87 # ----------------------------
94 # ----------------------------
96 # Note that all of the keys on the editing keypad transmit escape sequences. A
97 # vt220 does this only when in vt220 mode; when emulating a vt100 the editing
100 # Alternative keycodes:
101 # --------------------
102 # Several of the function keys have alternative names, depending on the type of
103 # host which your xterm is connected to. DEC (i.e., the VMS system) uses F15
104 # as the HELP key, F16 as the DO key. Unix applications generally do not do
105 # this. Curses applications in particular, assign a unique keycode to each
106 # capability string. These terminal descriptions do not have conflicting
107 # definitions, to ensure that Unix curses applications use a consistent set of
108 # keycodes. To get a VMS-bias, make these substitutions:
109 # 1. change khome to kfnd
110 # 2. change kend to kslt
111 # The original xterm-r6 entry does in fact have a VMS bias.
113 # Some legacy applications using the termcap emulation may expect kll where
114 # we have specified kend.
116 # Function keys with modifiers (Sun/PC):
117 # -------------------------------------
118 # Shift-Fx - kf{12+x}
119 # Control-Fx - kf{24+x}
120 # Shift-Control-Fx - kf{36+x}
122 # The terminfo defines some special keys which are documented as "shifted",
123 # e.g., kDC is shifted-delete-character.
125 # Note however, that even though the terminfo says a key might be sent, there
126 # may be conflicts which prevent this. For example, it is common to use
127 # shifted pageup and pagedown for window manager functions. The default
128 # translation for xterm since X11R4 has overridden shifted Insert, Select,
129 # PageUp and PageDown, which correspond to terminfo kIC, kEND, kPRV and kNXT
132 xterm-new|modern xterm terminal emulator,
142 # Encode modifiers using parameters (see "Xterm Control Sequences" ctlseqs.ms).
143 # Note that this is unrelated to PCTERM.
145 # Some names are extensions allowed by ncurses, e.g.,
146 # kDN, kDN5, kDN6, kLFT5, kLFT6, kRIT5, kRIT6, kUP, kUP5, kUP6
148 # The uppercase names are made up, since there are no standards that apply.
149 # If they were limited to two characters, they could in principle be translated
150 # to termcap. However, termcap sizes are limited to 1023 bytes, so there is
151 # little point in ensuring that extended key names can be translated to
152 # termcap. A terminfo file can be up to 4096 bytes; using all extended keys
153 # that xterm can generate would in fact exceed that limit.
155 # The numbers correspond to the modifier parameters documented in Xterm
164 # 8 Shift + Alt + Control
166 # X/Open Curses defines some shift combinations, which are also used here
167 # where applicable. Since it does define some shift combinations, no number
168 # (2) is used for suffixing the made-up names. Some combinations are not
169 # useful, e.g., they may reboot your computer, or they may require too many
170 # fingers. I stopped at modifier 7, just to keep things simple -TD
174 # The xterm+pcfn, xterm+pcf0, xterm+pcf1, xterm+pcf2 and xterm+pcf3 fragments
175 # correspond to default resource settings for xterm on a 104-key PC keyboard
176 # with 12 function-keys:
179 # *oldXtermFKeys:false
180 # *modifyCursorKeys:2
181 # *modifyFunctionKeys:2
184 # The key numbers are computed based on the modifiers:
186 # kf1-kf12 are F1-F12
187 # kf13-kf24 are shift F1-F12
188 # kf25-kf36 are control F1-F12
189 # kf37-kf48 are control+shift F1-F12
190 # kf49-kf60 are alt F1-F12
191 # kf61-kf63 are shift-alt F1-F3
193 # Note that ncurses would allow definition of kf64 and beyond, if there were
194 # an application that required it.
196 xterm+pcfkeys|fragment for PC-style keys,
202 # The ctrlFKeys resource is only relevant to the xterm+pcfn and xterm+pcfN
203 # entries, since the modifyFunctionKeys resource overrides ctrlFKeys when it is
204 # positive. A different choice of ctrlFKeys would give a different set of
205 # function-key strings.
206 xterm+pcfn|fragment with modifyFunctionKeys:-1 and ctrlFKeys:10,
256 # Changing ctrlFKeys to 12 would let us number the keys using just shift- and
257 # control- modifiers:
258 # kf1-kf12 are F1-F12
259 # kf13-kf24 are shift F1-F12
260 # kf25-kf36 are control F1-F12
261 # kf37-kf48 are control+shift F1-F12
262 xterm+pcfN|fragment with modifyFunctionKeys:-1 and ctrlFKeys:12,
312 xterm+pcf0|fragment with modifyFunctionKeys:0,
377 # This is almost the same as xterm+pcf2 because the unmodified keys all happen
378 # to have a pattern that forces the modifier to the same position.
379 xterm+pcf1|fragment with modifyFunctionKeys:1,
444 xterm+pcf2|fragment with modifyFunctionKeys:2,
509 xterm+pcf3|fragment with modifyFunctionKeys:3,
574 # The "PC-style" modifier scheme was introduced in xterm patch #94 (1999/3/27)
575 # and revised in patch #167 (2002/8/24).
577 # The original assignments from patch #94 for cursor-keys had some technical
580 # A parameter for a function-key to represent a modifier is just more
581 # bits. But for a cursor-key it may change the behavior of the
582 # application. For instance, emacs decodes the first parameter of a
583 # cursor-key as a repeat count.
585 # A parameterized string should (really) not begin with SS3 (\EO).
586 # Rather, CSI (\E[) should be used.
588 # For these reasons, the original assignments were deprecated. For
589 # compatibility reasons, they are still available as a setting of xterm's
590 # modifyCursorKeys resource. These fragments list the modified cursor-keys
591 # that might apply to xterm+pcfkeys with different values of that resource.
592 xterm+pcc3|fragment with modifyCursorKeys:3,
620 xterm+pcc2|fragment with modifyCursorKeys:2,
648 xterm+pcc1|fragment with modifyCursorKeys:1,
676 xterm+pcc0|fragment with modifyCursorKeys:0,
704 # The home/end keys on the editing keypad are also treated as cursor keys.
705 xterm+pce3|fragment with modifyCursorKeys:3,
744 xterm+pce2|fragment with modifyCursorKeys:2,
783 xterm+pce1|fragment with modifyCursorKeys:1,
822 xterm+pce0|fragment with modifyCursorKeys:0,
861 # This chunk is used for building the VT220/Sun/PC keyboard variants.
862 xterm-basic|modern xterm terminal emulator - common,
877 acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
884 cnorm=\E[?12l\E[?25h,
886 csr=\E[%i%p1%d;%p2%dr,
893 cup=\E[%i%p1%d;%p2%dH,
905 flash=\E[?5h$<100/>\E[?5l,
915 is2=\E[!p\E[?3;4l\E[4l\E>,
936 rs2=\E[!p\E[?3;4l\E[4l\E>,
940 setb=\E[4%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m,
941 setf=\E[3%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m,
942 sgr=%?%p9%t\E(0%e\E(B%;\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m,
958 # xterm-debian is identical to xterm-new except that it more strictly
959 # conforms to DEC VT220 behavior in the case of the backspace key; this is
960 # mandated by the Section 9.8 of the Debian Policy Manual. Also see
961 # <http://vt100.net/docs/vt220-rm/>.
962 xterm-debian|Debian xterm (VT220-conformant backspace),
968 # The xterm-new description has all of the features, but is not completely
969 # compatible with vt220. If you are using a Sun or PC keyboard, set the
970 # sunKeyboard resource to true:
971 # + maps the editing keypad
972 # + interprets control-function-key as a second array of keys, so a
973 # 12-fkey keyboard can support vt220's 20-fkeys.
974 # + maps numeric keypad "+" to ",".
975 # + uses DEC-style control sequences for the application keypad.
977 # Some packagers modify xterm's resource definitions to provide extra function
978 # keys by using the shift-modifier in the translations resource. However, that
979 # interferes with the DECUDK functionality.
981 xterm-vt220|xterm emulating vt220,
1022 xterm-vt52|xterm emulating dec vt52,
1026 acsc=``aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
1033 cup=\EY%p1%' '%+%c%p2%' '%+%c,
1050 # Sun does not number the function keys this way in their sparse termcap; their
1051 # terminal descriptions ignore the keypads. kb(7M) states that there are codes
1052 # reserved for 64 function keys, 16 each in left, right, top and bottom. Each
1053 # keyboard type has a different number of function keys in different
1054 # arrangements. Using xkeycaps for reference:
1056 # Type 3: left 10, top 9, right 15
1058 # kf1-kf9 are XK_F1-XK_F9
1059 # There is no kf10 on this keyboard type.
1060 # kf11-kf20 are keysyms XK_L1 through XK_L10.
1061 # kf31-kf45 are keysyms XK_R1 through XK_R15.
1063 # However, X's keysymdef.h is hard-coded to make
1066 # by someone who was unfamiliar with terminal types other than Sun's. So
1067 # xterm uses the internal X keysymbols, but the terminfo entry uses the Sun
1070 # Type 4: left 11, top 12, right 15
1072 # The left-keypad contains an unnumbered Help-key.
1073 # The right-keypad also contains NumLock, Ins, Del, Enter, + and - keys which
1074 # do not appear to be part of the R-sequence.
1076 # Type 5: left 9, top 12, right (more than one keypad)
1078 # These keyboards do not use the same naming convention, look like a hybrid of
1079 # the type 4 and IBM keyboards.
1083 # Set the modifyFunctionKeys resource to negative (-1) to make it simple to
1084 # enter the higher function-key values using shift- and control-modifiers.
1086 xterm-sun|xterm with sun function keys,
1137 xterm-hp|xterm with hpterm function keys,
1159 # scoterm implements 48 function-keys using shift- and control-modifiers to
1160 # multiple 12 function-keys. X has a hard-coded limit of 35 function-keys,
1161 # but xterm can represent larger values.
1165 # Set the modifyFunctionKeys resource to negative (-1) to make it simple to
1166 # enter the higher function-key values using shift- and control-modifiers.
1168 # Also, set ctrlFKeys resource to 12 (the default is 10) to make xterm see 48
1169 # function-keys on a keyboard with 12 function-keys and 4 control/shift
1170 # modifier combinations.
1172 xterm-sco|xterm with SCO function keys,
1230 # Other variants (these are all very old entries, from X11R5):
1231 xterm-24|xterms|vs100|xterm terminal emulator (X Window System),
1234 xterm-65|xterm with tall window 65x80 (X Window System),
1237 xterm-bold|xterm with bold instead of underline (X Window System),
1241 xterm-boldso|xterm with bold for standout (X Window System),
1245 xterm-mono|monochrome xterm,
1258 # VTxxx terminals are usually set up so that full-screen applications will use
1259 # the cursor application mode strings. This is good for full-screen
1260 # applications, including legacy applications which may have hard-coded
1261 # behavior, but bad for interactive shells (e.g., tcsh, bash) which use arrow
1262 # keys to scroll through a history of command strings.
1264 # To see the difference between normal/application modes, consider this example:
1265 # + In normal (non-application) mode, the terminal transmits a down-arrow
1266 # as \E[C, which happens to echo as a down-arrow.
1267 # + In application mode the terminal transmits \EOC, which echoes as C.
1268 # That is because the \EO is the SS3 control, which says to use the
1269 # character from the G3 character set for the next cell.
1271 # One example of hard-coded behavior would be for applications written to work
1272 # with VT52 and VT100 terminals. If the application's parser ignores 'O' and
1273 # '?' characters after the escape, then the cursor and keypad strings for the
1274 # two terminals are the same. (Indeed, one of the first curses applications
1275 # which I used did something like this to cover "ANSI" terminals -TD).
1277 # To make this work (leaving the cursor keys in normal mode), we have to adjust
1278 # the terminal initialization sequences:
1280 # smkx/rmkx set/reset the cursor and keypad application modes. We retain
1281 # the latter (otherwise many applications fail).
1283 # smcup/rmcup set/restore cursor-addressing mode for full-screen
1284 # applications. For xterm, this normally means the alternate
1285 # screen, which is not compatible with interactive shells. Some
1286 # programs are "smart" and disable these.
1288 xterm-noapp|xterm with cursor keys in normal mode,
1296 xterm+noapp|fragment with cursor keys in normal mode,
1303 xterm+app|fragment with cursor keys in application mode,
1310 xterm+noapp+pc|fragment for noapp pc-style home/end,
1314 xterm+app+pc|fragment for app pc-style home/end,
1318 xterm+edit|fragment for 6-key editing-keypad,
1325 xterm+decedit|fragment for vt220 6-key editing-keypad,
1332 xterm+pc+edit|fragment for pc-style editing keypad,
1336 xterm+vt+edit|fragment for vt220-style editing keypad,
1341 # This should work for the commonly used "color xterm" variations (XFree86
1342 # xterm, color_xterm, nxterm, rxvt). Note that it does not set 'bce', so for
1343 # XFree86 and and rxvt, some applications that use colors will be less
1344 # efficient, and in a few special cases (with "smart" optimization) the wrong
1345 # color will be painted in spots.
1346 xterm-color|generic "ANSI" color xterm (X Window System),
1355 # vi may work better with this entry, because vi
1356 # doesn't use insert mode much
1357 xterm-ic|xterm-vi|xterm with insert character instead of insert mode,
1365 # This is used only for testing (it's not relevant to DEC VTxxx terminals, but
1367 xterm-xmc|xterm with magic-cookie glitch,
1371 # This one also is primarily for testing ncurses; while the ISO 6429 defines
1372 # the REP control, none of the DEC VTxxx terminals (VT52 through VT420) support
1374 xterm-rep|xterm with repeat-character control,
1375 rep=%p1%c\E[%p2%{1}%-%db,
1378 # This is mainly for testing xterm; the real VT220 will not let you switch
1379 # character sets without first altering the keyboard language in the setup
1380 # screen. Some emulators allow this anyway. (Note that these strings are
1381 # normally used only for printers). The parameter to csnm and scs is the same
1382 # in both cases: the keyboard language parameter returned by CSI ? 2 6 n.
1383 xterm-nrc|xterm with VT220 national replacement character sets,
1384 csnm=%?%p1%{1}%=%tNorth American%e%p1%{2}%=%tBritish%e%p1%{3}%=%tFlemish%e%p1%{4}%=%tFrench Canadian%e%p1%{5}%=%tDanish%e%p1%{6}%=%tFinnish%e%p1%{7}%=%tGerman%e%p1%{8}%=%tDutch%e%p1%{9}%=%tItalian%e%p1%{10}%=%tSwiss (French)%e%p1%{11}%=%tSwiss (German)%e%p1%{12}%=%tSwedish%e%p1%{13}%=%tNorwegian%e%p1%{14}%=%tFrench/Belgian%e%p1%{15}%=%tSpanish%;,
1385 scs=%?%p1%{1}%=%t\E(B%e%p1%{2}%=%t\E(A%e%p1%{3}%=%t\E(R%e%p1%{4}%=%t\E(9%e%p1%{5}%=%t\E(E%e%p1%{6}%=%t\E(5%e%p1%{7}%=%t\E(K%e%p1%{8}%=%t\E(4%e%p1%{9}%=%t\E(Y%e%p1%{10}%=%t\E(=%e%p1%{11}%=%t\E(=%e%p1%{12}%=%t\E(7%e%p1%{13}%=%t\E(E%e%p1%{14}%=%t\E(R%e%p1%{15}%=%t\E(Z%;,
1388 # Foreground 0-15 maps (with toggles) into 30-37 & 90-97
1389 # Background 0-15 maps (with toggles) into 40-47 & 100-107
1391 # Originally I suppressed setaf/setab, since ANSI specifies only 8 colors, but
1392 # Stephen Marley persuaded me to allow the "ANSI" color controls to extend to
1393 # 16 colors. (Note that ncurses 4.2 uses setf/setb from this description;
1394 # however 5.0 selects either according to their availability). - T.Dickey
1396 # SVr4 curses does not use more than 8 colors anyway, so using 16 colors is
1397 # either for terminfo-level applications or via ncurses.
1398 xterm-16color|xterm with 16 colors,
1401 setab=\E[%?%p1%{8}%<%t%p1%{40}%+%e%p1%{92}%+%;%dm,
1402 setaf=\E[%?%p1%{8}%<%t%p1%{30}%+%e%p1%{82}%+%;%dm,
1403 setb=%p1%{8}%/%{6}%*%{4}%+\E[%d%p1%{8}%m%Pa%?%ga%{1}%=%t4%e%ga%{3}%=%t6%e%ga%{4}%=%t1%e%ga%{6}%=%t3%e%ga%d%;m,
1404 setf=%p1%{8}%/%{6}%*%{3}%+\E[%d%p1%{8}%m%Pa%?%ga%{1}%=%t4%e%ga%{3}%=%t6%e%ga%{4}%=%t1%e%ga%{6}%=%t3%e%ga%d%;m,
1407 # This uses RGB values 0..1000
1409 # 256 colors should give 65536 pairs, but terminfo stores numbers in a signed
1410 # short. Most people will not notice problems with only 32767 pairs.
1411 xterm-256color|xterm with 256 colors,
1415 initc=\E]4;%p1%d;rgb\:%p2%{255}%*%{1000}%/%2.2X/%p3%{255}%*%{1000}%/%2.2X/%p4%{255}%*%{1000}%/%2.2X\E\\,
1416 setab=\E[%?%p1%{8}%<%t4%p1%d%e%p1%{16}%<%t10%p1%{8}%-%d%e48;5;%p1%d%;m,
1417 setaf=\E[%?%p1%{8}%<%t3%p1%d%e%p1%{16}%<%t9%p1%{8}%-%d%e38;5;%p1%d%;m,
1421 xterm-88color|xterm with 88 colors,
1426 # This is an 8-bit version of xterm, which emulates DEC vt220 with ANSI color.
1427 # To use it, your decTerminalID resource must be set to 200 or above, and the
1428 # sunKeyboard resource set to true.
1435 xterm-8bit|xterm terminal emulator with 8-bit controls (X Window System),
1451 acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
1458 cnorm=\233?25l\233?25h,
1460 csr=\233%i%p1%d;%p2%dr,
1467 cup=\233%i%p1%d;%p2%dH,
1479 flash=\233?5h$<100/>\233?5l,
1489 is2=\E[62"p\E G\233m\233?7h\E>\E7\233?1;3;4;6l\2334l\233r\E8,
1547 rs2=\E[62"p\E G\233m\233?7h\E>\E7\233?1;3;4;6l\2334l\233r\E8,
1551 setb=\2334%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m,
1552 setf=\2333%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m,
1553 sgr=\2330%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m%?%p9%t\E(0%e\E(B%;,
1569 xterm-xf86-v44|xterm terminal emulator (XFree86 4.4 Window System),
1585 acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
1592 cnorm=\E[?12l\E[?25h,
1594 csr=\E[%i%p1%d;%p2%dr,
1601 cup=\E[%i%p1%d;%p2%dH,
1614 flash=\E[?5h$<100/>\E[?5l,
1625 is2=\E[!p\E[?3;4l\E[4l\E>,
1715 rs2=\E[!p\E[?3;4l\E[4l\E>,
1719 setb=\E[4%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m,
1720 setf=\E[3%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m,
1721 sgr=\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m%?%p9%t\016%e\017%;,
1740 xterm-xfree86|xterm terminal emulator (XFree86 4.4 Window System),
1743 # Compatible with the R6 xterm, with the following changes:
1744 # + added acsc (perhaps some versions of tic assume the standard vt100
1745 # alternate character set)
1746 # + added u6, u7, u8, u9 strings for Daniel Weaver's tack program.
1747 # + added kmous string for ncurses.
1748 # + added khome/kend strings (which conflict with kfnd/kslt, see note).
1749 xterm-r6|xterm-old|xterm X11R6 version,
1759 acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
1764 csr=\E[%i%p1%d;%p2%dr,
1771 cup=\E[%i%p1%d;%p2%dH,
1787 is2=\E[m\E[?7h\E[4l\E>\E7\E[r\E[?1;3;4;6l\E8,
1821 rmcup=\E[2J\E[?47l\E8,
1826 rs2=\E[m\E[?7h\E[4l\E>\E7\E[r\E[?1;3;4;6l\E8,
1842 # Compatible with the R5 xterm, with the following changes:
1843 # + changed 'blink=@', to 'blink@' (the former meant that "@" would start
1844 # a blink, the latter that it is not supported).
1845 # + changed kf1 through kf4 to correspond with actual usage. Though X
1846 # supports keypad symbols for PF1 to PF4, and xterm interprets these
1847 # correctly, the F1 to F4 codes are commonly (but incorrectly) used.
1848 # + moved reset string from rs1 to rs2, to correlate better with termcap.
1849 # + make khome consistent with other entries.
1850 # + use rmul/smul, rmir/smir from termcap, but not rmcup/smcup because
1851 # not everyone wants the alternate screen.
1852 # + added u6, u7, u8, u9 strings for Daniel Weaver's tack program.
1853 # + added kmous string for ncurses.
1854 xterm-r5|xterm R5 version,
1867 csr=\E[%i%p1%d;%p2%dr,
1874 cup=\E[%i%p1%d;%p2%dH,
1926 rs2=\E>\E[?1;3;4;5;6l\E[4l\E[?7h\E[m\E[r\E[2J\E[H,
1928 sgr=\E[%?%p1%t;7%;%?%p2%t;4%;%?%p3%t;7%;%?%p4%t;5%;%?%p6%t;1%;m,
1941 # Customization begins here.
1943 # This is the only entry which you should have to customize, since "xterm"
1944 # is widely used for a variety of incompatible terminal emulations including
1945 # color_xterm and rxvt.
1946 xterm|X11 terminal emulator,