|
 |
a1ffe7 |
diff -Naur gpm-1.20.7.orig/doc/doc.gpm.in gpm-1.20.7/doc/doc.gpm.in
|
|
|
a1ffe7 |
--- gpm-1.20.7.orig/doc/doc.gpm.in 2012-10-26 23:21:38.000000000 +0200
|
|
|
a1ffe7 |
+++ gpm-1.20.7/doc/doc.gpm.in 2013-07-19 19:40:33.374213536 +0200
|
|
|
a1ffe7 |
@@ -600,7 +600,7 @@
|
|
|
a1ffe7 |
that one of @t{\-o dtr}, @t{\-o rts}, @t{\-o both} can be specified to
|
|
|
a1ffe7 |
toggle the control lines of the serial port.
|
|
|
a1ffe7 |
|
|
|
a1ffe7 |
-The following mouse type are corrently recognized:
|
|
|
a1ffe7 |
+The following mouse type are currently recognized:
|
|
|
a1ffe7 |
|
|
|
a1ffe7 |
@table @code
|
|
|
a1ffe7 |
@item bare Microsoft
|
|
|
a1ffe7 |
@@ -621,7 +621,7 @@
|
|
|
a1ffe7 |
this is your case, use the @samp{bare} mouse type. Some new
|
|
|
a1ffe7 |
two-button devices are ``plug and play'', and they don't play
|
|
|
a1ffe7 |
fair at all; in this case try @t{\-t pnp}. Many (most)
|
|
|
a1ffe7 |
- three-button devices that use the microsoft protocol fail to
|
|
|
a1ffe7 |
+ three-button devices that use the Microsoft protocol fail to
|
|
|
a1ffe7 |
report some middle-button events during mouse motion. Since
|
|
|
a1ffe7 |
the protocol does not distinguish between the middle button
|
|
|
a1ffe7 |
going up and the middle button going down it would be liable
|
|
|
a1ffe7 |
@@ -649,7 +649,7 @@
|
|
|
a1ffe7 |
decoder gets into a confused state where it thinks the middle
|
|
|
a1ffe7 |
button is up when it's down and vice versa. (If you get sick
|
|
|
a1ffe7 |
of having to do this, please don't blame gpm; blame your buggy
|
|
|
a1ffe7 |
- mouse! Note that most three-button mice that do the microsoft
|
|
|
a1ffe7 |
+ mouse! Note that most three-button mice that do the Microsoft
|
|
|
a1ffe7 |
protocol can be made to do the MouseSystems protocol
|
|
|
a1ffe7 |
instead. The ``3 Button Serial Mouse mini-HOWTO'' has
|
|
|
a1ffe7 |
information about this.) This mouse decoder accepts standard
|