X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=misc%2Fterminfo.src;h=a9d4225f5a3083ebd65a8efa681d5533c70666b4;hp=8078639c796da75e3ecd91db12db9db2816041e1;hb=b0b1980be11bba618d84beb8b30ac94e2c820602;hpb=6be6b9d9202ba34ee545955dc66e355d9855353a diff --git a/misc/terminfo.src b/misc/terminfo.src index 8078639c..a9d4225f 100644 --- a/misc/terminfo.src +++ b/misc/terminfo.src @@ -6,8 +6,8 @@ # Report bugs and new terminal descriptions to # bug-ncurses@gnu.org # -# $Revision: 1.508 $ -# $Date: 2014/06/14 21:16:34 $ +# $Revision: 1.525 $ +# $Date: 2014/10/19 01:16:56 $ # # The original header is preserved below for reference. It is noted that there # is a "newer" version which differs in some cosmetic details (but actually @@ -4164,19 +4164,6 @@ xterm-256color|xterm with 256 colors, xterm-88color|xterm with 88 colors, use=xterm+88color, use=xterm-256color, -# These two are used to demonstrate the any-event mouse support, i.e., by -# using an extended name "XM" which tells ncurses to put the terminal into -# a special mode when initializing the xterm mouse. -xterm+sm+1002|testing xterm-mouse, - XM=\E[?1002%?%p1%{1}%=%th%el%;, use=xterm-new, -xterm+sm+1003|testing xterm-mouse, - XM=\E[?1003%?%p1%{1}%=%th%el%;, use=xterm-new, - -xterm-1002|testing xterm-mouse, - use=xterm+sm+1002, use=xterm-new, -xterm-1003|testing xterm-mouse, - use=xterm+sm+1003, use=xterm-new, - # This chunk is based on suggestions by Ailin Nemui and Nicholas Marriott, who # asked for some of xterm's advanced features to be added to its terminfo # entry. It defines extended capabilities not found in standard terminfo or @@ -4378,6 +4365,132 @@ xterm-nic|xterm with ich/ich1 suppressed for non-curses programs, xterm1|xterm terminal emulator ignoring the alternate screen buffer, rmcup@, smcup@, use=xterm, +#### XTERM Mouse +# The xterm mouse protocol is used by other terminal emulators. +# In this section, two extended capabilities are used to illustrate the mouse +# protocol: XM and xm. The "XM" capability is recognized by ncurses to allow +# enabling/disabling other mouse protocols. The "xm" capability describes the +# mouse response; currently there is no interpreter which would use this +# information to make the mouse support completely data-driven. + +# Here is the "original" xterm mouse protocol. +# +# First seen in X10.3, February 1986, this likely dates from 1985 based on the +# copyright dates in the sources. A comment in charproc.c notes "MIT bogus +# sequence", referring to the fact that it does not correspond to a "real" +# terminal. The mouse responses for the X10 protocol are sent only for +# button-presses. +xterm+x10mouse|X10 xterm mouse protocol, + kmous=\E[M, XM=\E[?9%?%p1%{1}%=%th%el%;, + xm=\E[M%p3%' '%+%c%p2%'!'%+%c%p1%'!'%+%c, +xterm-x10mouse|X10 xterm mouse, + use=xterm+x10mouse, use=xterm, + +# Here is the conventional xterm mouse protocol, introduced with X11R1 in +# September 1987. +# +# The mouse responses for the X11 protocol covered button releases, as well as +# modifiers: +# shift 4 +# alt/meta 8 (technically the "mod1" mask, because X11 has no such keys) +# control 16 +# +# The modifiers are not reflected in this description because as used in xterm +# they are normally inaccessible because the translations resources assign +# shift and control to other features. However, they are important because +# they take up space in the first byte of the response. The other bits of this +# byte are used to encode the button number for both presses and releases. +# In the X11 protocol, any button-release is encoded with "3" (the lowest 2 +# bits in the byte). Later work on XFree86 xterm used the remaining 3 bits to +# provide additional features, e.g., wheel mouse. +# +# X11R1's xterm also supported an "emacs" mouse protocol, with final character +# "t" or "T", which was activated by double-clicking. The "t" response was +# used when the starting/ending positions were the same. +# +# X11R3 (February 1988) added the highlight/tracking mode. +# +# X11R4 (December 1989) added the control sequences document, listing the +# control sequences for the X10/X11 protocols without descriptions. It also +# mentioned the "emacs" ("T") response. Comments in button.c referred to the +# X11 protocol as "DEC vt200 compatible", although DEC offered no such terminal. +# +# X11R5 (November 1993) gave a description of the mouse protocol. +# +# X11R6 (January 1995) moved the control sequences document out of the xterm +# source-directory to xc/doc/specs/xterm, polishing the formatting but adding +# no new information. +xterm+x11mouse|X11 xterm mouse protocol, + kmous=\E[M, XM=\E[?1000%?%p1%{1}%=%th%el%;, + xm=\E[M%?%p4%t3%e%p3%' '%+%c%;%p2%'!'%+%c%p1%'!'%+%c, +xterm-x11mouse|X11 mouse, + use=xterm+x11mouse, use=xterm, + +# Here is a suggested description of the xterm highlighting protocol. +# A more complicated example could be constructed to account for the "t" +# response. +xterm+x11hilite|X11 xterm mouse protocol with highlight, + kmous=\E[M, XM=\E[?1001%?%p1%{1}%=%th%el%;, + xm=\E[%p7%'!'%+%p6%'!'%+%c%p9%'!'%+%c%p8%'!'%+%c%p2%'!'%+%c%p1%'!'%+%cT, +xterm-x11hilite|X11 mouse with highlight, + use=xterm+x11mouse, use=xterm, + +# The preceding were the sources from X Consortium. Other sources (or patches) +# were available. Starting in mid-1995, XFree86 developers collected some of +# those changes and began improvements, e.g., to support color. This was, by +# the way, around the same time that rxvt developers began implementing color, +# though dates (and attributions) are not well documented. I became interested +# in xterm in late 1995, and involved in early 1996. To complete the picture, +# CDE's dtterm was introduced around the same time, with no mouse protocol -TD + +# xterm patch #83 (1998/10/7), added Jason Bacon's changes to provide an +# "any-event" mouse mode. +xterm+sm+1002|xterm any-event mouse, + kmous=\E[M, XM=\E[?1002%?%p1%{1}%=%th%el%;, +xterm-1002|xterm any-event mouse, + use=xterm+sm+1002, use=xterm, + +xterm+sm+1003|testing xterm-mouse, + kmous=\E[M, XM=\E[?1003%?%p1%{1}%=%th%el%;, + +xterm-1003|testing xterm-mouse, + use=xterm+sm+1003, use=xterm, + +# xterm patch #116 (1999/9/25) added Stephen P Wall's changes to support DEC +# locator mode. + +# xterm patch #120 (1999/10/28) added my change to support wheel mouse, by +# dropping support for the X11 mouse protocol's shift-modifier and using +# available bits in the first byte of the response to encode buttons 4 and 5. +# xterm patch #126 (2000/2/8) amended that change to avoid conflicting with +# older configurations which might have used the obsolete modifiers. + +# xterm patch #262 (2010/8/30) added Ryan Johnson's changes to provide a mode +# where the coordinates in the mouse response would be encoded in UTF-8, +# thereby extending the range of coordinates past 222=(255-33). This is the +# "1005" mouse mode. +xterm+sm+1005|xterm UTF-8 mouse, + kmous=\E[M, XM=\E[?1005;1000%?%p1%{1}%=%th%el%;, + xm=\E[M%?%p4%t3%e%p3%' '%+%c%;%p2%'!'%+%u%p1%'!'%+%u, +xterm-1005|xterm UTF-8 mouse, + use=xterm+sm+1005, use=xterm, + +# xterm patch #277 (2012/1/7) provides a mode where the mouse response uses +# SGR-style parameters. +# +# Someone stated that the 1005 mouse mode would not be handled properly in luit. +# (By the way, this is a problem with the X11 protocol). A more plausible +# criticism is that the responses provided by the 1005 mode are not distinct +# from the non-1005 responses. +# +# As an alternative (and fixing the longstanding limitation of X11 mouse +# protocol regarding button-releases), I provided this: +xterm+sm+1006|xterm SGR-mouse, + kmous=\E[<, XM=\E[?1006;1000%?%p1%{1}%=%th%el%;, + xm=\E[<%p1%d;%p2%d;%p3%d;%?%p4%tM%em%;, +xterm-1006|xterm SGR-mouse, + use=xterm+sm+1006, use=xterm, + #### KTERM # (kterm: this had extension capabilities ":KJ:TY=ascii:" -- esr) # (kterm should not invoke DEC Graphics as the alternate character set @@ -5004,6 +5117,25 @@ rxvt+pcfkeys|fragment for PC-style fkeys, kLFT5=\EOd, kNXT5=\E[6\^, kNXT6=\E[6@, kPRV5=\E[5\^, kPRV6=\E[5@, kRIT5=\EOc, kUP=\E[a, kUP5=\EOa, +# rxvt was originally "xvt", first announced in April 1993: +# http://www.informatica.co.cr/linux-desktops/research/1993/0416.html +# +# Though its change-log does not mention this, John Davis has stated that he +# was the author of the changes to use the bce ("new color model") which was +# incorporated into rxvt 2.11 (June 15, 1995). The change-log does not give +# dates, nor give developer's names. Initial color support was added for rxvt +# "2.0", which was sometime in 1994. +# +# rxvt had usable color support with 2.16 (April 2, 1996), with some help by my work on +# vttest, as well as bug reports to Mark Olesen. For instance, the fix +# mentioned here +# http://web.archiveorange.com/archive/v/6ETvLb5wHtbbzCaS4S9J +# was from one of my bug-reports -TD +# +# While the color model both for xterm and rxvt was based on Linux console, +# Olesen (or possibly Davis) diverged in one respect from Linux's bce color +# behavior: inserting/deleting characters does not fill the newly empty cell +# with the default background color. rxvt|rxvt terminal emulator (X Window System), ncv@, hpa=\E[%i%p1%dG, kf0=\E[21~, sgr0=\E[m\017, @@ -5033,6 +5165,23 @@ rxvt-16color|xterm with 16 colors like aixterm, # # mrxvt is based on rxvt 2.7.11, but has by default XTERM_FKEYS defined, which # makes its function-keys different from other flavors of rxvt -TD +# +# Testing with tack: +# + made custom description (below) to work, though it sets TERM=xterm. +# +# Testing with vttest: +# + While "based on" rxvt, some of the basic functionality is broken. The +# window collapses to a single line when running several of the screens +# in vttest, e.g., the tests for cursor movement, screen features, +# double-sized characters. +# + The vt52 test works properly, but this is an exception. Due to the +# other bug(s) most of vttest is untestable. +# + the color test using ECH shows a gap in the bce model, like rxvt. +# +# Testing with xterm "vttest" scripts: +# + resize.pl does not work because mrxvt does implement CSI 18 t +# (not in rxvt, but not documented by mrxvt) but not CSI 19 t. +# + none of the "dynamic colors" (OSC colors) scripts work. mrxvt|multitabbed rxvt, XT, kEND=\E[8;2~, kHOM=\E[7;2~, kcub1=\E[D, kcud1=\E[B, @@ -5553,7 +5702,7 @@ terminator|Terminator no line wrap, #### TERMINOLOGY # http://enlightenment.org # -# Tested terminology-0.3.0, using tack and vttest. This is not a vt100 +# Tested terminology-0.3.0, 0.6.1, using tack and vttest. This is not a vt100 # emulator, nor is it compatible with xterm, but it uses a few features from # both -TD # @@ -5569,20 +5718,21 @@ terminator|Terminator no line wrap, # no blink # uses bce model for colors, but (see below) fails the vttest screens # has partial support for 256color feature. -# tack cursor-keys: +# tack function-keys (a subset of xterm+pcf0), and +# tack cursor-keys (a subset of xterm+pce2): # ctrl+shift (ignored) # 2 shift # shift-alt modifier -> shift (2) # 3 alt # 4 # 5 ctrl -# tack modifiers do not work for fkeys +# tack modifiers did not work for fkeys in 0.3.0; subset works in 0.6.1 # ctrl + khome/kend works - none of the other modifiers do # vttest - # spits lots of messages from termptyesc.c especially in vttest. # no 132-column mode # fails menu 1, 2 (definitely not vt100-compatible) -# primary and +# primary (claims vt420 with several options, apparently none work) and # secondary report says (perhaps... vt420): \E[>41;285;0c # CHA, HPR, VPA, CNL, CPL work # BCE with ED/EL - fail @@ -5593,6 +5743,10 @@ terminator|Terminator no line wrap, # X10 and Normal mouse work # Any-event mouse works # Mouse button-event works +# +# This description uses xterm+pcf0, which is misleading because the program +# does not handle combinations of modifiers - but listing them all would +# involve more effort than its developers spent -TD terminology|EFL-based terminal emulator, mc5i@, xon@, blink@, ed@, el@, el1@, invis=\E[8m, kLFT=\E[1;2D, @@ -5607,7 +5761,7 @@ terminology|EFL-based terminal emulator, kLFT3=\E[1;3D, kLFT4=\E[1;4D, kLFT5=\E[1;5D, kLFT6=\E[1;6D, kLFT7=\E[1;7D, kRIT3=\E[1;3C, kRIT4=\E[1;4C, kRIT5=\E[1;5C, kRIT6=\E[1;6C, - kRIT7=\E[1;7C, kUP=\E[1;2A, use=vt100, + kRIT7=\E[1;7C, kUP=\E[1;2A, use=xterm+pcf0, use=vt100, use=xterm+256setaf, ######## UNIX VIRTUAL TERMINALS, VIRTUAL CONSOLES, AND TELNET CLIENTS @@ -21809,7 +21963,18 @@ v3220|LANPAR Vision II model 3220/3221/3222, # TS is a string capability which acts like "tsl", but uses no parameter and # goes to the first column of the "status line". # XM is a string capability which overrides ncurses's built-in string which -# enables xterm mouse mode. +# enables/disables xterm mouse mode. +# xm shows the format of the mouse responses. Parameters are (from zero): +# p1 = y-ordinate +# p2 = x-ordinate +# p3 = button +# p4 = state, e.g., pressed or released +# p6 = y-ordinate starting region +# p7 = x-ordinate starting region +# p8 = y-ordinate ending region +# p9 = x-ordinate ending region +# Other extensions, used in xm: +# %u = UTF-8 # #### Miscellaneous extensions: # @@ -23394,4 +23559,18 @@ v3220|LANPAR Vision II model 3220/3221/3222, # + add dim, invis capabilities to vte-2012 -TD # + add sitm/ritm to konsole-base and mlterm3 -TD # +# 2014-10-06 +# + add xterm-1005 and xterm-1006 entries, with suggested extension +# capability "xm" -TD +# +# 2014-10-07 +# + update test-report for mrxvt -TD +# +# 2014-10-11 +# + add xterm-x10mouse, xterm-x11mouse, etc. -TD +# +# 2014-10-18 +# + reviewed terminology 0.6.1, add function key definitions. None of +# the vt100-compatibility issues were improved -TD +# ######## SHANTIH! SHANTIH! SHANTIH!