| 1 |
.TH MEV 1 "February 1995" |
| 2 |
.UC 4 |
| 3 |
.SH NAME |
| 4 |
mev \- a program to report mouse events |
| 5 |
.SH SYNOPSIS |
| 6 |
.B mev |
| 7 |
[ |
| 8 |
.I options |
| 9 |
] |
| 10 |
.br |
| 11 |
.SH DESCRIPTION |
| 12 |
The `mev' program is part of the gpm package. |
| 13 |
The information below is extracted from the texinfo file, which is the |
| 14 |
preferred source of information. |
| 15 |
|
| 16 |
.LP |
| 17 |
The mev program is modeled after xev. It prints to stdout the |
| 18 |
mouse console events it gets. |
| 19 |
|
| 20 |
.LP |
| 21 |
mev's default behaviour is to get anything, but command line switches |
| 22 |
can be used to set the various fields in the Gpm_Connect structure, in |
| 23 |
order to customize the program's behaviour. I'm using mev to |
| 24 |
handle mouse events to Emacs. |
| 25 |
|
| 26 |
.LP |
| 27 |
Command line switches for mev are the following: |
| 28 |
.TP |
| 29 |
\-C \fBnumber\fP |
| 30 |
Select a virtual console to get events from. |
| 31 |
This is intended to be used for debugging. |
| 32 |
.TP |
| 33 |
\-d \fBnumber\fP |
| 34 |
Choose a default mask. By default the server gets |
| 35 |
any events not belonging to the event mask. The mask can be |
| 36 |
provided either as a |
| 37 |
decimal number, or as a symbolic string. |
| 38 |
.TP |
| 39 |
\-e \fBnumber\fP |
| 40 |
Choose the event mask. By default any event |
| 41 |
is received. The mask can be provided either as a |
| 42 |
decimal number, or as a symbolic string. |
| 43 |
.TP |
| 44 |
\-E |
| 45 |
Enter emacs mode. In emacs mode events are reported as |
| 46 |
lisp forms rather than numbers. This is the format used by the |
| 47 |
t-mouse package within emacs. |
| 48 |
.TP |
| 49 |
\-f |
| 50 |
Fit events inside the screen before reporting them. This options |
| 51 |
re-fits drag events, which are allowed to exit the screen border, |
| 52 |
|
| 53 |
.TP |
| 54 |
\-i |
| 55 |
Interactive. Accepts input from stdin to change connection |
| 56 |
parameters. |
| 57 |
.TP |
| 58 |
\-m \fBnumber\fP |
| 59 |
Choose the minimum modifier mask. Any event with |
| 60 |
fewer modifiers will not be reported to mev. It defaults to 0. |
| 61 |
The mask must be provided either as a |
| 62 |
decimal number, or as a symbolic string. |
| 63 |
.TP |
| 64 |
\-M \fBnumber\fP |
| 65 |
Choose the maximum modifier mask. Any event with |
| 66 |
more modifier than specified will not be reported to mev. |
| 67 |
It defaults to \~~0, i.e. all events are received. |
| 68 |
The mask must be provided either as a |
| 69 |
decimal number, or as a symbolic string. |
| 70 |
.TP |
| 71 |
\-p |
| 72 |
Requests to draw the pointer during drags. This option is used |
| 73 |
by emacs to avoid invoking ioctl() from lisp code. |
| 74 |
|
| 75 |
.LP |
| 76 |
When the arguments are not decimal integers, they are considered lists |
| 77 |
of alphanumeric characters, separated by a single non-alphanumeric |
| 78 |
character. I use the comma (,), but any will do. |
| 79 |
|
| 80 |
.LP |
| 81 |
Allowed names for events are move, drag, down or |
| 82 |
press, up or release, motion (which is both |
| 83 |
move and drag), and hard. |
| 84 |
|
| 85 |
.LP |
| 86 |
Allowed names for modifiers are shift, leftAlt, |
| 87 |
rightAlt, anyAlt (one or the other), control. |
| 88 |
|
| 89 |
.LP |
| 90 |
When the \-i switch is specified, mev looks at its standard input as |
| 91 |
command lines rather than events. The input lines are parsed, and the |
| 92 |
commands push and pop are recognized. |
| 93 |
|
| 94 |
.LP |
| 95 |
The push command, then, accepts the options \-d, \-e, \-m |
| 96 |
and \-M, with the same meaning described above. Unspecified options |
| 97 |
retain the previous value and the resulting masks are used to reopen |
| 98 |
the connection with the server. pop is used to pop the connection |
| 99 |
stack. If an empty stack is popped the program exits. |
| 100 |
|
| 101 |
.LP |
| 102 |
Other commands recognized are info, used to return the stack |
| 103 |
depth; quit to prematurely terminate the program; and |
| 104 |
snapshot to get some configuration information from the server. |
| 105 |
|
| 106 |
.LP |
| 107 |
.SH BUGS |
| 108 |
Beginning with release 1.16, \fBmev\fP no longer works under xterm. |
| 109 |
Please use the \fBrmev\fP program (provided in the \fBsample\fP |
| 110 |
directory) to watch gpm events under xterm or rxvt. \fBrmev\fP also |
| 111 |
displays keyboard events besides mouse events. |
| 112 |
|
| 113 |
.LP |
| 114 |
.SH AUTHOR |
| 115 |
Alessandro Rubini <[email protected]> |
| 116 |
.br |
| 117 |
Ian Zimmerman <[email protected]> |
| 118 |
|
| 119 |
.LP |
| 120 |
.SH FILES |
| 121 |
.nf |
| 122 |
/dev/gpmctl The socket used to connect to gpm. |
| 123 |
.fi |
| 124 |
|
| 125 |
.LP |
| 126 |
.SH SEE ALSO |
| 127 |
.nf |
| 128 |
\fB gpm(8) \fP The mouse server |
| 129 |
\fB gpm-types(7) \fP Description of mouse types supported by gpm. |
| 130 |
|
| 131 |
.fi |
| 132 |
The info file about `gpm', which gives more complete information and |
| 133 |
explains how to write a gpm client. |