X-Git-Url: http://ncurses.scripts.mit.edu/?a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fuser_caps.5.html;h=8626b0b43b14257ea218f316dcca6f4cef31a705;hb=04d942c3d98cf0a929c6afb17be8c10d4ae39af0;hp=6d6e9126a28025603d05d3a89f0262fe6fefb1fe;hpb=8f6d94b8d6211a2323caef53fa4c96c475ec9a62;p=ncurses.git
diff --git a/doc/html/man/user_caps.5.html b/doc/html/man/user_caps.5.html
index 6d6e9126..8626b0b4 100644
--- a/doc/html/man/user_caps.5.html
+++ b/doc/html/man/user_caps.5.html
@@ -1,6 +1,7 @@
@@ -237,6 +238,72 @@
XM string, override ncurses's built-in string which enables/disables
xterm mouse mode.
+ ncurses sends a character sequence to the terminal to initialize
+ mouse mode, and when the user clicks the mouse buttons or (in
+ certain modes) moves the mouse, handles the characters sent back
+ by the terminal to tell it what was done with the mouse.
+
+ The mouse protocol is enabled when the mask passed in the mouse-
+ mask function is nonzero. By default, ncurses handles the
+ responses for the X11 xterm mouse protocol. It also knows about
+ the SGR 1006 xterm mouse protocol, but must to be told to look
+ for this specifically. It will not be able to guess which mode
+ is used, because the responses are enough alike that only confu-
+ sion would result.
+
+ The XM capability has a single parameter. If nonzero, the mouse
+ protocol should be enabled. If zero, the mouse protocol should
+ be disabled. ncurses inspects this capability if it is present,
+ to see whether the 1006 protocol is used. If so, it expects the
+ responses to use the SGR 1006 xterm mouse protocol.
+
+ The xterm mouse protocol is used by other terminal emulators.
+ The terminal database uses building-blocks for the various xterm
+ mouse protocols which can be used in customized terminal descrip-
+ tions.
+
+ The terminal database building blocks for this mouse feature also
+ have an experimental capability xm. The "xm" capability
+ describes the mouse response. Currently there is no interpreter
+ which would use this information to make the mouse support com-
+ pletely data-driven.
+
+ xm shows the format of the mouse responses. In this experimental
+ capability, the parameters are
+
+ p1 y-ordinate
+
+ p2 x-ordinate
+
+ p3 button
+
+ p4 state, e.g., pressed or released
+
+ p5 y-ordinate starting region
+
+ p6 x-ordinate starting region
+
+ p7 y-ordinate ending region
+
+ p8 x-ordinate ending region
+
+ Here are examples from the terminal database for the most com-
+ monly used xterm mouse protocols:
+
+ xterm+x11mouse|X11 xterm mouse protocol,
+ kmous=\E[M, XM=\E[?1000%?%p1%{1}%=%th%el%;,
+ xm=\E[M
+ %?%p4%t%p3%e%{3}%;%' '%+%c
+ %p2%'!'%+%c
+ %p1%'!'%+%c,
+
+ xterm+sm+1006|xterm SGR-mouse,
+ kmous=\E[<, XM=\E[?1006;1000%?%p1%{1}%=%th%el%;,
+ xm=\E[<%i%p3%d;
+ %p1%d;
+ %p2%d;
+ %?%p4%tM%em%;,
+
Several terminals provide the ability to send distinct strings for com-
@@ -305,6 +372,14 @@
tic(1m), infocmp(1m).
+ The terminal database section NCURSES USER-DEFINABLE CAPABILITIES sum-
+ marizes commonly-used user-defined capabilities which are used in the
+ terminal descriptions. Some of those features are mentioned in
+ screen(1) or tmux(1).
+
+ XTerm Control Sequences provides further information on the xterm fea-
+ tures which are used in these extended capabilities.
+
Thomas E. Dickey