Searched refs:motion (Results 1 - 3 of 3) sorted by relevance
| /freebsd-current/contrib/nvi/vi/ |
| H A D | vi.c | 137 * motion. If it does, we get it too, calling its underlying
171 * any motion component goes away, i.e. "d3w2." deletes a
196 * Do any required motion; v_motion sets the from MARK and the
281 * its motion, the count was used only for the motion.
301 * motion component. Other similar commands (e.g. +, -) don't
419 * The O_TILDEOP option makes the ~ command take a motion instead
429 "[count]~[count]motion",
430 " ~ change case to motion"
439 * [count] [buffer] [count] key [[motion] | [buffe
719 VICMD motion; local
[all...] |
| H A D | vi.h | 35 * succeed if they were associated with a motion command, and fail
43 * motion routines know what's really going on.
46 * functions (motion component or command) as well. For this reason,
83 * Commands that can be motion components set the end of the range
96 * as a motion component. The general rules are as follows:
98 * 1: If not a motion component, the final cursor is at the end
105 * Usually, if moving backward in the file and it's a motion component,
222 VICMD cmd; /* Current command, motion. */
223 VICMD motion; member in struct:_vi_private
230 VICMD sdot; /* Saved dot, motion comman
[all...] |
| /freebsd-current/sys/contrib/xen/io/ |
| H A D | kbdif.h | 265 * rel_x - int32_t, relative X motion
266 * rel_y - int32_t, relative Y motion
267 * rel_z - int32_t, relative Z motion (wheel)
325 * rel_z - int32_t, relative Z motion (wheel)
353 * with a down event, followed by zero or more motion events,
402 * Multi-touch motion event
505 struct xenkbd_motion motion; member in union:xenkbd_in_event
|
Completed in 161 milliseconds