Note: This is still work in progress and only works on Linux X11, with little wayland support.
Navigate GUIs without a mouse by typing hints in combination with modifier keys.
- click once (jk)
- click multiple times (2jk)
- right click (SHIFT + jk)
- drag (ALT + jk)
- hover (CTRL + jk)
- scroll/move the mouse using vim key bindings (h,j,k,l)
Don't like the keybindings? That's ok, you can change them.
-
You will need to have some sort of compositing setup so that you can properly overlay hints over windows with the correct level of transparency. Otherwise, the overlay will just cover the entire screen; not allowing you to see what is under the overlay.
-
You will need to enable accessibility for your system. If you use a Desktop Environment, this might already be enabled by default. Otherwise, there is a guide here, take a look at "5 Troubleshooting".
-
Install hints:
Below you will find installation instructions for some popular linux distros bases. The setup is as follows:
- Install the python/system dependencies (including pipx).
- Setup pipx.
- Use pipx to install hints.
Ubuntu
sudo apt update && \
sudo apt install git libgirepository1.0-dev gcc libcairo2-dev pkg-config python3-dev gir1.2-gtk-4.0 pipx && \
pipx ensurepath && \
pipx install git+https://github.com/AlfredoSequeida/hints.git
Fedora
sudo dnf install git gcc gobject-introspection-devel cairo-gobject-devel pkg-config python3-devel gtk4 pipx && \
pipx ensurepath && \
pipx install git+https://github.com/AlfredoSequeida/hints.git
Arch
sudo pacman -Sy && \
sudo pacman -S git python cairo pkgconf gobject-introspection gtk4 python-pipx && \
pipx ensurepath && \
pipx install git+https://github.com/AlfredoSequeida/hints.git
Finally, source your shell config or restart your terminal.
At this point, hints should be installed, you can verify this by running hints
in your shell. You will want to bind a keyboard shortcut to hints
so you don't have to keep typing in a command to open it. This will depend on your OS/ window manager / desktop environment.
Here is an example of a binding on i3 by editing .conf/i3/config
:
bindsym $mod+i exec hints
This will bind mod + i to launch hints. To stop showing hints (quit hints), press the Esc key on your keyboard.
Hints also has a scroll mode to scroll, which can also be bound to a key combination. For example:
bindsym $mod+y exec hints --mode scroll
If you still don't see any hints, the application you're testing could need a bit of extra setup. Please see the Help,-hints-doesn't-work-with-X-application page in the wiki.
For a guide on configuring and using hints, please see the Wiki.
The easiest ways to contribute are to:
- Become a sponsor. Hints is a passion project that I really wanted for myself and I am working on it on my spare time. I chose to make it free and open source so that others can benefit. If you find it valuable, donating is a nice way to say thanks. You can donate any amount you want.
- Report bugs. If you notice something is not working as expected or have an idea on how to make hints better, open up an issue. This helps everyone out.
- If you can code, feel free to commit some code! You can see if any issues need solutions or you can create a new feature. If you do want to create a new feature, it's a good idea to create an issue first so we can align on why this feature is needed and if it has a possibility of being merged.
If you want to help develop hints, first setup your environment:
- Create a virtual environment for the project.
python3 -m venv venv
-
Activate your virtual environment for development. This will differ based on OS/shell. See the table here for instructions.
-
Install hints as an editable package (from the repositorie's root directory):
pip install -e .
At this point, hints should be installed locally in the virtual environment, you can run hints
in your shell to launch it. Any edits you make to the source code will automatically update the installation. For future development work, you can simply re-enable the virtual environment (step 2).
- If you are making updates that impact hints, you will most likely need to test displaying hints and might find yourself executing hints but not being quick enough to switch to a window to see hints. To get around this, you can execute
hints
with a short pause in your shell:sleep 0.5; hints
. This way you can have time to switch to a window and see any errors / logs in your shell.