||1 year ago|
|.github||2 years ago|
|assets||1 year ago|
|contrib||1 year ago|
|docs||1 year ago|
|src||1 year ago|
|.gitignore||2 years ago|
|.rustfmt.toml||2 years ago|
|CODE_OF_CONDUCT.md||2 years ago|
|CONTRIBUTING.md||2 years ago|
|Cargo.toml||1 year ago|
|INSTALL.md||1 year ago|
|LICENSE||2 years ago|
|README.md||1 year ago|
|com.github.sohkd.pkexec.policy||1 year ago|
|rust-toolchain.toml||1 year ago|
A next-generation hotkey daemon for Wayland/X11 written in Rust.
Simple Odilia HotKey Daemon
sohkd is a display protocol-independent hotkey daemon made in Rust. sohkd uses an easy-to-use configuration system inspired by sxhkd so you can easily add or remove hotkeys.
It also attempts to be a drop-in replacement for swhkd, meaning your sxhkd config file is also compatible with sohkd.
Because sohkd can be used anywhere, the same sohkd config can be used across Xorg or Wayland desktops, and you can even use sohkd in a tty.
Installation and Building:
swhks & pkexec sohkd
After opening sohkd, you can control the program through signals:
sudo pkill -USR1 sohkd- Pause key checking
sudo pkill -USR2 sohkd- Resume key checking
sudo pkill -HUP sohkd- Reload config file
Swhkd closely follows sxhkd syntax, so most existing sxhkd configs should be functional with sohkd.
The default configuration file is in
/etc/sohkd/sohkdrc. If you don't like having to edit the file as root every single time, you can create a symlink from
If you use Vim, you can get sohkd config syntax highlighting with the
sohkd-vim plugin. Install it in
All supported key and modifier names are listed in
man 5 sohkd-keys.
To autostart sohkd you can do one of two things:
- Add the commands from the "Running" section to your window managers configuration file.
- Enable the service file for your respective init system. Currently only systemd and OpenRC service files exist and more will be added soon including Runit.
We use a server-client model to keep you safe. The daemon ( sohkd - privileged process ) communicates to the server ( swhks - running as non root user ) after checking for valid keybinds. Since the daemon is totally separate from the server, no other process can read your keystrokes. As for shell commands, you might be thinking that any program can send shell commands to the server and that's true! But the server runs the commands as the currently logged in user so no extra permissions are provided ( This is essentially the same as any app on your desktop calling shell commands ).
So yes, you're safe!