[xboxdrv] 05/06: Update fix-xboxdrv-manpage.patch.

Andrey Rahmatullin wrar-guest at moszumanska.debian.org
Sun Mar 20 13:50:44 UTC 2016


This is an automated email from the git hooks/post-receive script.

wrar-guest pushed a commit to branch master
in repository xboxdrv.

commit b6a659b7130f933a293261528ccf3b66872eeadf
Author: Andrey Rahmatullin <wrar at wrar.name>
Date:   Sun Mar 20 18:14:14 2016 +0500

    Update fix-xboxdrv-manpage.patch.
---
 debian/patches/fix-xboxdrv-manpage.patch | 136 ++++++++++++++++++++++++++++---
 1 file changed, 125 insertions(+), 11 deletions(-)

diff --git a/debian/patches/fix-xboxdrv-manpage.patch b/debian/patches/fix-xboxdrv-manpage.patch
index 0be9f66..b5ccfb8 100644
--- a/debian/patches/fix-xboxdrv-manpage.patch
+++ b/debian/patches/fix-xboxdrv-manpage.patch
@@ -1,11 +1,11 @@
 Description: Fix xboxdrv.1 errors reported by lintian
  Fix all hyphen-used-as-minus-sign and spelling-error-in-manpage reports.
-Author: Andrey Rahmatullin <wrar at wrar.name>
+Author: Andrey Rahmatullin <wrar at debian.org>
 Forwarded: no
-Last-Update: 2012-02-03
+Last-Update: 2016-03-20
 
 diff --git a/doc/xboxdrv.1 b/doc/xboxdrv.1
-index d801ea7..b3b7bd3 100644
+index d801ea7..2ed5c33 100644
 --- a/doc/xboxdrv.1
 +++ b/doc/xboxdrv.1
 @@ -56,7 +56,7 @@ for more information.
@@ -37,6 +37,15 @@ index d801ea7..b3b7bd3 100644
  endpoint \*(T<\fBgeneric\-usb\fR\*(T> will read. The
  spec as the form
  of \fINAME=VALUE,...\fR. Allowed values are:
+@@ -727,7 +727,7 @@ Add a modifier to the modifier stack, see
+ a full list of possible modifier.
+ .TP 
+ \*(T<\fB\-\-timeout \fR\*(T>\fIMSEC\fR
+-Specify the number of miliseconds that xboxdrv will wait
++Specify the number of milliseconds that xboxdrv will wait
+ for events from the controller before moving on and
+ processing things like auto-fire or relative-axis.
+ Default value is 10, smaller values will give you a
 @@ -789,7 +789,7 @@ T}
  T{
  lt(7), rt(8)
@@ -64,6 +73,15 @@ index d801ea7..b3b7bd3 100644
  mapping. In addition you can supply a sign to indicate that an axis
  should be inverted. So if you want to invert the y1 axis start with:
  
+@@ -840,7 +840,7 @@ the order in which the options are given.
+ .TP 
+ \*(T<\fB\-\-autofire BUTTON=FREQUENCY,...\fR\*(T>
+ Autofire mapping allows you to let a button automatically fire with a
+-given frequency in miliseconds:
++given frequency in milliseconds:
+ 
+ .nf
+ \*(T<$ xboxdrv \-\-autofire A=250\*(T>
 @@ -854,7 +854,7 @@ as autofire while another one, emitting the same signal, acts normally.
  .fi
  .TP 
@@ -82,7 +100,7 @@ index d801ea7..b3b7bd3 100644
  will generally give good results, everything beyond that
  won't be of much practical use.
  
-@@ -946,7 +946,7 @@ Will give you controls that are relative to your
+@@ -946,12 +946,12 @@ Will give you controls that are relative to your
  character instead of your viewpoint.
  .TP 
  \*(T<\fB\-\-four\-way\-restrictor\fR\*(T>
@@ -91,6 +109,12 @@ index d801ea7..b3b7bd3 100644
  limit the movement on both analogsticks to only four
  directions (up, down, left, right), the diagonals (up/left,
  up/right, down/left, down/right) are filtered out from the
+ output. This option is useful for games such as Tetris, that
+-don't need diagonals and where you don't want to accidently
++don't need diagonals and where you don't want to accidentally
+ trigger the down-move while trying to do a left/right move.
+ .TP 
+ \*(T<\fB\-\-relative\-axis AXIS=NUM,...\fR\*(T>
 @@ -1082,7 +1082,7 @@ switch this behaviour off.
  \*(T<\fB\-\-device\-name NAME\fR\*(T>
  Changes the descriptive name the device will have. This
@@ -109,15 +133,31 @@ index d801ea7..b3b7bd3 100644
  .TP 
  \*(T<\fB\-\-device\-usbids TYPE.SLOT=VENDOR:PRODUCT:VERSION:BUS,...\fR\*(T>
  Changes the vendor, product, version and bus id the device will
-@@ -1292,7 +1292,7 @@ is \fIVALUE\fR * axis_state.
- gives the number of milisecond to pass before the event
+@@ -1177,7 +1177,7 @@ event. In that case you can supply additional paramaters in the form of:
+ \fIVALUE\fR gives the value of the event (default: 10)
+ 
+ \fIREPEAT\fR
+-gives the number of milisecond to pass before the event
++gives the number of millisecond to pass before the event
+ is fired again (default: 5)
+ 
+ The special 'void' event allows you to clear any
+@@ -1289,12 +1289,12 @@ is \fIVALUE\fR * axis_state.
+ (default: 10)
+ 
+ \fIREPEAT\fR
+-gives the number of milisecond to pass before the event
++gives the number of millisecond to pass before the event
  is fired again (default: 5).
  
 -The value of -1 has a special meaning, it will result in
 +The value of \-1 has a special meaning, it will result in
  the REL event being fired as soon as possible (i.e.
- every \fItimeout\fR miliseconds).
+-every \fItimeout\fR miliseconds).
++every \fItimeout\fR milliseconds).
  This is the recomment way for handling mouse emulation,
+ as it will keep REL events syncronized and thus avoid
+ jaggies in the movement, that will result from manually
 @@ -1345,7 +1345,7 @@ handler, while \*(T<\fBKEY_A\fR\*(T> is an argument for the
  event handler. What kind of arguments an event handler allows
  depends on the event handler.
@@ -127,6 +167,27 @@ index d801ea7..b3b7bd3 100644
  just writing:
  .PP
  .nf
+@@ -1380,9 +1380,9 @@ An example for the hold button would look like:
+ 
+ This will send JS_0 events when the button is pressed
+ and switch to JS_1 events when the button was hold for
+-500 miliseconds.
++500 milliseconds.
+ 
+-The hold button feature is useful to effectly double the
++The hold button feature is useful to effectively double the
+ number of available buttons, thus the dpad can for
+ example be used to send out eight different button
+ events instead of just four, which is enough to handle
+@@ -1396,7 +1396,7 @@ The rel handler will send out a REL event whenever the
+ button is pressed. \fIVALUE\fR
+ gives the value of the event that will be send,
+ while \fIREPEAT\fR gives the number
+-of miliseconds till the event will be send again.
++of milliseconds till the event will be send again.
+ 
+ A typical use for REL events is emulation of the scroll
+ wheel of a mouse, an example configuration would be:
 @@ -1465,7 +1465,7 @@ To move backwards through the sequence another key must
  be bound to \*(T<\fBsequence\-key\-ref\fR\*(T>.
  .TP 
@@ -136,16 +197,32 @@ index d801ea7..b3b7bd3 100644
  when the button was pressed. An example would look like
  this:
  
-@@ -1544,7 +1544,7 @@ is \fIVALUE\fR * axis_state.
- gives the number of milisecond to pass before the event
+@@ -1541,12 +1541,12 @@ is \fIVALUE\fR * axis_state.
+ (default: 10)
+ 
+ \fIREPEAT\fR
+-gives the number of milisecond to pass before the event
++gives the number of millisecond to pass before the event
  is fired again (default: 5).
  
 -The value of -1 has a special meaning, it will result in
 +The value of \-1 has a special meaning, it will result in
  the REL event being fired as soon as possible (i.e.
- every \fItimeout\fR miliseconds).
+-every \fItimeout\fR miliseconds).
++every \fItimeout\fR milliseconds).
  This is the recomment way for handling mouse emulation,
-@@ -1599,7 +1599,7 @@ when it is not pressed and in unpressed state when it is
+ as it will keep REL events syncronized and thus avoid
+ jaggies in the movement, that will result from manually
+@@ -1577,7 +1577,7 @@ in \fIVALUE\fR, by
+ scaling \fIREPEAT\fR instead that
+ problem is worked around.
+ .SH "INPUT FILTER"
+-Input filter allow to manipulate the events that come from the
++Input filters allow one to manipulate the events that come from the
+ controller. They can be used
+ on \*(T<\fB\-\-buttonmap\fR\*(T>, \*(T<\fB\-\-axismap\fR\*(T>, \*(T<\fB\-\-ui\-buttonmap\fR\*(T>
+ and \*(T<\fB\-\-ui\-axismap\fR\*(T>. The difference between the
+@@ -1599,15 +1599,15 @@ when it is not pressed and in unpressed state when it is
  pressed.
  .TP 
  \*(T<\fBauto\fR\*(T>, \*(T<\fBautofire\fR\*(T>:\fIRATE\fR:\fIDELAY\fR
@@ -154,6 +231,25 @@ index d801ea7..b3b7bd3 100644
  press events when the button is held down. It takes two
  optional parameters:
  
+ \fIRATE\fR is the number of
+-miliseconds between button press events.
++milliseconds between button press events.
+ 
+ \fIDELAY\fR the amount of
+-miliseconds till the autofire will start, before that
++milliseconds till the autofire will start, before that
+ delay the button will act as normal.
+ .TP 
+ \*(T<\fBclick\-press\fR\*(T>
+@@ -1631,7 +1631,7 @@ signal a game or another application which configuration
+ is currently active.
+ .TP 
+ \*(T<\fBdelay\fR\*(T>:\fITIME\fR
+-A button has to be held down for TIME miliseconds before
++A button has to be held down for TIME milliseconds before
+ it will emit an event, press events shorter then that will
+ be ignored.
+ .TP 
 @@ -1752,7 +1752,7 @@ If you want to permanently unload it add the following line to
  .fi
  .PP
@@ -199,6 +295,15 @@ index d801ea7..b3b7bd3 100644
  .SS EVTEST
  evtest lets you read raw input events from \*(T<\fI/dev/input/eventX\fR\*(T>. The
  event devices are the very core of all event handling, things like the
+@@ -2060,7 +2060,7 @@ Start xboxdrv with:
+ Your right analog stick will act as trottle control, the
+ trigger as rudder. Using \*(T<\fB\-\-modifier\fR\*(T> to
+ install a four-way restrictor might also be worth a
+-consideration to not accidently touch the throttle when the
++consideration to not accidentally touch the throttle when the
+ rudder is moved.
+ .SS "USING MOUSE EMULATION AND JOYSTICK AT THE SAME TIME"
+ To use mouse emulation and joystick at the same time you have
 @@ -2206,7 +2206,7 @@ If you have success with that, send a patch
  to <\*(T<grumbel at gmail.com\*(T>>, if not, contact me too, I
  might be able to provide additional help.
@@ -208,6 +313,15 @@ index d801ea7..b3b7bd3 100644
  enforce a USB device as well as a controller type an bypass any auto
  detection.
  .SS "\(dqUNKNOWN DATA: BYTES: 3 DATA: ...\(dq"
+@@ -2237,7 +2237,7 @@ itself works with:
+ .fi
+ .SS "THE WIRELESS CONTROLLER DOESN'T WORK"
+ You have to sync the controller befor it can be used, restart of the
+-driver isn't needed and the driver should let you now when it recieves
++driver isn't needed and the driver should let you now when it receives
+ a connection after you sync the controller.
+ .SS "KEYBOARD EMULATION"
+ When you try to let xboxdrv send a keyboard events
 @@ -2349,7 +2349,7 @@ And insert the following lines:
  .fi
  .SS "PERMANENT WORKAROUND BY DISABLING DEVICE AUTO DETECTION"

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-games/xboxdrv.git



More information about the Pkg-games-commits mailing list