swhkd is a display protocol-independent hotkey daemon made in Rust. swhkd uses an easy-to-use configuration system inspired by sxhkd so you can easily add or remove hotkeys.
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 sxhkd, meaning your sxhkd config file is also compatible with swhkd.
It also attempts to be a drop-in replacement for swhkd, meaning your sxhkd config file is also compatible with sohkd.
Because swhkd can be used anywhere, the same swhkd config can be used across Xorg or Wayland desktops, and you can even use swhkd in a tty.
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:
@ -30,49 +30,44 @@ Because swhkd can be used anywhere, the same swhkd config can be used across Xor
```bash
swhks &
pkexec swhkd
pkexec sohkd
```
## Runtime signals:
After opening swhkd, you can control the program through signals:
After opening sohkd, you can control the program through signals:
- `sudo pkill -USR1 swhkd` - Pause key checking
- `sudo pkill -USR2 swhkd` - Resume key checking
- `sudo pkill -HUP swhkd` - Reload config file
- `sudo pkill -USR1 sohkd` - Pause key checking
- `sudo pkill -USR2 sohkd` - Resume key checking
- `sudo pkill -HUP sohkd` - Reload config file
## Configuration:
Swhkd closely follows sxhkd syntax, so most existing sxhkd configs should be functional with swhkd.
Swhkd closely follows sxhkd syntax, so most existing sxhkd configs should be functional with sohkd.
The default configuration file is in `/etc/swhkd/swhkdrc`. If you don't like having to edit the file as root every single time, you can create a symlink from `~/.config/swhkd/swhkdrc` to `/etc/swhkd/swhkdrc`.
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 `~/.config/sohkd/sohkdrc` to `/etc/sohkd/sohkdrc`.
If you use Vim, you can get swhkd config syntax highlighting with the
[swhkd-vim](https://github.com/waycrate/swhkd-vim) plugin. Install it in
vim-plug with `Plug 'waycrate/swhkd-vim'`.
If you use Vim, you can get sohkd config syntax highlighting with the
[sohkd-vim](https://github.com/waycrate/sohkd-vim) plugin. Install it in
vim-plug with `Plug 'waycrate/sohkd-vim'`.
All supported key and modifier names are listed in `man 5 swhkd-keys`.
All supported key and modifier names are listed in `man 5 sohkd-keys`.
## Autostart:
### To autostart swhkd you can do one of two things:
### To autostart sohkd you can do one of two things:
1. Add the commands from the ["Running" section](https://github.com/waycrate/swhkd#running) to your window managers configuration file.
1. Enable the [service file](https://github.com/waycrate/swhkd/tree/main/contrib/init) for your respective init system. Currently only systemd and OpenRC service files exist and more will be added soon including Runit.
1. Add the commands from the ["Running" section](https://github.com/waycrate/sohkd#running) to your window managers configuration file.
1. Enable the [service file](https://github.com/waycrate/sohkd/tree/main/contrib/init) for your respective init system. Currently only systemd and OpenRC service files exist and more will be added soon including Runit.
## Security:
We use a server-client model to keep you safe. The daemon ( swhkd - 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 ).
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 ).
Tait Hoyem
2 years ago