warpd(1)
A modal keyboard driven pointer manipulation program.
warpd [options]
*-f*, *--foreground*: Run warpd in the foreground. Mainly useful for debugging.
*-l*, *--list-keys*: Print a list of valid keys which can be used as config values.
*--list-options*: Print all configurable options.
*-v*, *--version*: Print the current version.
*-c*, *--config* <config file>: Use the provided config file (- corresponds to stdin).Mode Flags:
*--hint*: Run warpd in (daemonless) hint mode.
*--hint2*: Run warpd in 2 stage hint mode.
*--grid*: Run warpd in grid mode.
*--normal*: Run warpd in normal mode.
*--history*: Run warpd in history hint mode.
*--screen*: Run warpd in screen selection mode.
*--oneshot*: When paired with one of the mode flags, exit warpd as soon as the mode is complete (i.e don't drop into normal mode). When used with normal mode, exit as soon as a mouse button is pressed (without pressing it). If no mode flag is specified, the default behaviour is the same as --normal --oneshot. Principally useful for scripting.
*-q*, *--query*: Consume a list of hints from stdin and print the result to stdout (in the form <x> <y> <hint>). Each line should have the form _<label> <x> <y>_. May be used in conjunction with --click.
*--drag*: Automatically start a drag operation when paired with --normal.
*--move '<x> <y>'*: Move the pointer to the specified coordinates and exit.
*--click <button>*: Send a mouse click corresponding to the supplied button and exit. May be paired with --move or --oneshot (in which case the click will occur at the end of the selection).
*--record*: When used with --click, adds the click event to warpd's history.warpd has three main modes which can be used to manipulate the pointer. The primary mode is called 'normal mode' (A-M-c) and facilitates local pointer movement using vi-like bindings (h j k l). The other two modes, hint and grid mode are used to effect larger movements across the screen and are expected to be used in combination with normal mode to achieve the desired end.
For example, the user might activate warpd in hint mode (A-M-x) to pinpoint the start of a text region before starting a drag operation (v) and ultimately using normal mode to complete the selection. If the selection is a large body of text, it may be desirable to activate grid (g) or hint (x) mode for a second time to warp the pointer to the desired region's terminal point.
In its simplest form, warpd can be used as a poor man's xdotool (--move/--click). Scrolling can be acheived by using e and y in normal mode. For a full list of bindings see --list-options.
A description of each mode follows (see also USAGE_NOTES):
This is the default mode (and the endpoint of both grid and normal mode) which is designed for short distance pointer manipulation. It is particularly useful for manipulating popup menus and selecting text (see Dragging). The default behaviour is vi-like. Pressing the mapped directional keys (default hjkl) moves the cursor in a continuous fashion, but the pointer can also be warped to the edges of the screen using the home (H), middle (M), and last (L) mappings. Finally, a numeric multiplier can be supplied to the directional keys as an input prefix in order to move the cursor by a proportional increment in the given direction (e.g 10j moves 10 units down).
This mode populates the screen with a list of labels and allows the user to immediately warp the pointer to a given location by pressing the corresponding key sequence. It is similar to functionality provided by browser plugins like Vimperator but works outside of the browser and indiscriminately covers the entire screen. Once a target has been selected 'normal mode' is entered for further manipulation.
Note: While it may at first be tempting to saturate the screen with hints, the user is cautioned against this. A balance must be struck between hint size, the number of hints, and the size of the screen. Enough space must be left to provide contextual awareness, while enough hints must be present to facilitate targetting UI elements without the need for too much adjustment. Once this equilibrium has been achieved, using hint mode become second nature and is (in the author's opinion) superior to grid mode for quickly pinpointing elements.
For finer movements, a two phase hint mode can be activated by pressing 'X' within normal mode.
Identical to hint mode but exclusively displays hints over previously selected targets.
By default grid mode divides the screen into a 2x2 grid. Each time a key is pressed the grid shrinks to cover the targeted quadrant. The cursor is placed in the middle of the grid.
covers the desired target a mouse button (e.g 'm') can be pressed.
E.G
+--------+--------+ +--------+--------+
| | | | u | i | |
| u | i | |----m----+ |
M-x | | | u | j | k | |
-----> +--------m--------+ -----> +---------+ |
| | | | |
| j | k | | |
| | | | |
+--------+--------+ +--------+--------+This mode is intended for multi-screen setups and provides the user with a dedicated set of hints for switching monitors and dropping them into normal mode.
Pressing v whilst in normal mode toggles a drag operation. The cursor can then be warped around the screen as normal in order to select text or move objects until the drag key is hit again or a mouse button is pressed. Additionally, the copy_and_exit key (c) may be used to copy the selected text to the system clipboard and terminate the current session.
Wayland's architecture does not allow clients to globally bind hotkeys. In order to run warpd, one of the mode flags must be used. These can be bound to the corresponding hotkeys in your compositor.
E.G
On sway:
bindsym Mod4+Mod1+x exec warpd --hint
bindsym Mod4+Mod1+c exec warpd --normal
bindsym Mod4+Mod1+g exec warpd --gridNon-wayland users should favour the daemon, since it also caches some of the draw operations to improve performance.
The program can be modified by placing configuration options in ~/.config/warpd/config, a complete list of which can be obtained with --list-options.
Each option must be specified on its own line and have the format:
:Options which take one or more keys may optionally be unset using the value "unbind".
-
Options which expect one or more keys may be specified multiple times, in which case all accepted mappings are interchangeable.
-
Options which accept multiple keys (e.g buttons) expect each key to be separated by a space.
-
For options expecting only a single key, it is possible to specify all desired bindings as space separated values in a single declaration.
-
If a key is bound to multiple config options, the most recently defined one takes precedence.
hint_mode: f ais identical to
hint_mode: f
hint_mode: aand will bind both f and a to hint mode activation keys.
while
buttons: m , .
buttons: j k lwill bind both the sequences m , . and j k l to mouse buttons 1 2 and 3 respectively. Note that the latter set of bindings override the default normal mode movements keys.
Judicious use of warpd's flags makes creating custom modes fairly easy.
For example, the --oneshot flag may be used in conjunction with one of the mode flags to facilitate target selection at which point subsequent action can be taken by the script.
# Prompt the user for a target using two stage hint mode and
# left click on the result.
#
# This particular example can be achieved more concisely with:
#
# warpd --hint2 --click 1
warpd --hint2 --oneshot; warpd --click 1
# Interactively create a hint file.
#
# Points can be added by navigating around as usual and pressing 'p'.
# The process is terminated by using the exit key.
warpd --normal|awk '{print substr("asdfghjkl;qwertyuiopzxcv,./;", NR, 1), $0}' > hints
# Prompt the user for one of the recorded hints and click on the
# result.
warpd --click 1 --query < hints The key to using warpd effectively is to learn when to exit normal mode. Much of one's time at a computer is spent moving the mouse between windows, interacting with UI elements, and reading text. What one might call 'browse mode'. It is in this mode of operation that it makes sense to keep warpd active.
Developing facility with the scroll and oneshot mouse buttons is key to achieving this. For example, if you happen to have two documents open and wish to switch between them, you can simply type x fx (where fx is a hint) if normal mode is already active. Scrolling can subsequently be achieved using e and r. Once you finally wish to type something, you can do x fx n to focus on the UI element, click, and exit.
Conversely, warpd can complement an input heavy workflow with its oneshot functionality and dedicated activation keys (E.G n, A-M-l, A-M-x, etc).
It is important to note that warpd is not intended to replace mouse heavy workflows, and will likely always be inferior for rapid precise local movements. When confronted with an IDE, or some other pointer driven abomination, the author still sometimes reaches for his mouse.
Activating discrete mode and pressing v can provide a familiar environment to a vi user but it is important to remember that cursor manipulation is application agnostic and consequently ignorant of the text on the screen. All movement is necessarily pixel based, consequently, drag + hint mode can be a superior method for surgically selecting text (though it may at first be less intuitive).
$XDG_CONFIG_HOME/warpd/config++ ~/.config/warpd/config The path of the configuration file (searched in order).
On error warpd will exit with a status of 255, otherwise the exit code will correspond to the button used to terminate warpd (in the case of oneshot buttons or in the presence of --oneshot). If warpd is terminated explicitly (i.e with the exit key) it will exit with a status of 0.
warpd uses various platform specific hacks to bypass limitations of the display server. All implementations were written by the same author, who presently uses X.
Consequently testing on non-X platforms has been minimal.
YMMV
Bugs can be reported here:
https://github.com/rvaiya/warpd/issues/
A list of known limitations follow:
-
Multiscreen support currently does not support hotplugging. This means that you must restart warpd after making any changes to your screen configuration.
-
For implementation reasons, the cursor position is not horizontally centered, but to the right of the actual pointer. This generally isn't an issue, but may become more noticeable as you increase cursor_size.
-
Unplugging the keyboard while warpd is one of its active modes will cause pandemonium. If you do this (don't :P), you may need to remotely ssh into the machine or switch to a VT to kill the process.
-
warpd uses Xinput for input processing to bypass certain limitation of the X input system. A byproduct of this is that certain remapping tools will not work (e.g xcape). If you are in the habit of making unorthodox changes to your keymap (like remapping capslock to control/escape) you may want to try an evdev based remapper like keyd (https://github.com/rvaiya/keyd).
-
Programs which use Xinput to directly manipulate input devices may misbehave. See Issue #3 for details.
- Cursor hiding relies on a hack that some programs ignore (e.g iTerm).
- Some programs (e.g iTerm) have a 'secure input mode' (which can usually be disabled) that causes interference.
- Cursor hiding doesn't work.
- Running as a daemon doesn't work (can't listen for hotkeys).
- UI elements (e.g input fields) which require focus can't be selected.
Written and maintained by Raheman Vaiya (2019-). See https://github.com/rvaiya/warpd for more information.