| 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 \fInumber\fP |
| 30 |
Select a virtual console to get events from. |
| 31 |
This is intended to be used for debugging. |
| 32 |
.TP |
| 33 |
\-d \fInumber\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 \fInumber\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 |
.TP |
| 53 |
\-i |
| 54 |
Interactive. Accepts input from `stdin' to change connection |
| 55 |
parameters. |
| 56 |
.TP |
| 57 |
\-m \fInumber\fP |
| 58 |
Choose the minimum modifier mask. Any event with |
| 59 |
fewer modifiers will not be reported to `mev'. It defaults to `0'. |
| 60 |
The mask must be provided either as a |
| 61 |
decimal number, or as a symbolic string. |
| 62 |
.TP |
| 63 |
\-M \fInumber\fP |
| 64 |
Choose the maximum modifier mask. Any event with |
| 65 |
more modifier than specified will not be reported to `mev'. |
| 66 |
It defaults to `\~~0', i.e. all events are received. |
| 67 |
The mask must be provided either as a |
| 68 |
decimal number, or as a symbolic string. |
| 69 |
.TP |
| 70 |
\-p |
| 71 |
Requests to draw the pointer during drags. This option is used |
| 72 |
by emacs to avoid invoking `ioctl()' from lisp code. |
| 73 |
|
| 74 |
.LP |
| 75 |
When the arguments are not decimal integers, they are considered lists |
| 76 |
of alphanumeric characters, separated by a single non-alphanumeric |
| 77 |
character. I use the comma (`,'), but any will do. |
| 78 |
|
| 79 |
.LP |
| 80 |
Allowed names for events are `move', `drag', `down' or |
| 81 |
`press', `up' or `release', `motion' (which is both |
| 82 |
`move' and `drag'), and `hard'. |
| 83 |
|
| 84 |
.LP |
| 85 |
Allowed names for modifiers are `shift', `leftAlt', |
| 86 |
`rightAlt', `anyAlt' (one or the other), `control'. |
| 87 |
|
| 88 |
.LP |
| 89 |
When the `\-i' switch is specified, `mev' looks at its standard input as |
| 90 |
command lines rather than events. The input lines are parsed, and the |
| 91 |
commands `push' and `pop' are recognized. |
| 92 |
|
| 93 |
.LP |
| 94 |
The `push' command, then, accepts the options `\-d', `\-e', `\-m' |
| 95 |
and `\-M', with the same meaning described above. Unspecified options |
| 96 |
retain the previous value and the resulting masks are used to reopen |
| 97 |
the connection with the server. `pop' is used to pop the connection |
| 98 |
stack. If an empty stack is popped the program exits. |
| 99 |
|
| 100 |
.LP |
| 101 |
Other commands recognized are `info', used to return the stack |
| 102 |
depth; `quit' to prematurely terminate the program; and |
| 103 |
`snapshot' to get some configuration information from the server. |
| 104 |
|
| 105 |
.LP |
| 106 |
.SH BUGS |
| 107 |
Beginning with release 1.16, \fBmev\fP no longer works under xterm. |
| 108 |
Please use the \fBrmev\fP program (provided in the \fBsample\fP |
| 109 |
directory) to watch gpm events under xterm or rxvt. \fBrmev\fP also |
| 110 |
displays keyboard events besides mouse events. |
| 111 |
|
| 112 |
.LP |
| 113 |
.SH AUTHOR |
| 114 |
Alessandro Rubini <[email protected]> |
| 115 |
.br |
| 116 |
Ian Zimmerman <[email protected]> |
| 117 |
|
| 118 |
.LP |
| 119 |
.SH FILES |
| 120 |
.nf |
| 121 |
/dev/gpmctl The socket used to connect to gpm. |
| 122 |
.fi |
| 123 |
|
| 124 |
.LP |
| 125 |
.SH SEE ALSO |
| 126 |
.nf |
| 127 |
\fB gpm(8) \fP The mouse server |
| 128 |
|
| 129 |
.fi |
| 130 |
The info file about `gpm', which gives more complete information and |
| 131 |
explains how to write a gpm client. |