A hotkey launcher
I created this because xbindkeys, sxhkd, dxhkd, etc. didn't launch new processes within the context of the current user's systemd default cgroup slice.
This causes a number of side effects, such as the following appearing in my journal after restarting
sxhkd.service: Found left-over process 1182850 (bash) in control group while starting unit. Ignoring.
This usually indicates unclean termination of a previous run, or service implementation deficiencies.
The output of all running commands would output to sxhkd's controlling terminal; since I personally start sxhkd as a service, the output shows up in the unit journal.
Not only that, but applications that quit unsuccessfully or dumped their cores stoped the sxhkd service, consequently necessitating a full restart of sxhkd.service. Since my application launcher (dmenu/rofi) is started by by sxhkd, I am only able to restart if I already have a terminal open or by switching to a different virtual console
Cactus solves this by decoupling execution context by adding an indireciton layer who's environment is controlled by systemd
- Choose shell or exec per command to use
- View list of all available commands so you don't have to remember it right away
- By default, pass arguments directly to exec-style function (faster startup)
- Execs out to
systemd-runbehind the scenes - Config hot reload (you may have to hover your mouse over interface for an update due to ImgGUI)
- Escape to close window
git clone https://github.com/hyperupcall/cactus cd cactus go install .
You can use cactus via the terminal, or launch via a traditional hotkey daemon
Ex. sxhkdrc
super + y cactus
Place configuration in $XDG_CONFIG_HOME/cactus/binds.toml. See ./share/sample.toml for details
You also must have a $XDG_CONFIG_HOME/cactus/cactus.toml. It can be blank
Find the full keymap list here
You may have issues with launching applications because the systemd slice may not match your current environment. Ammend your ~/.profile etc.
systemctl --user import-environment LANG LANGUAGE LC_ALL PATH XDG_CONFIG_HOME XDG_DATA_HOME
Remember, if you are launching cactus through another hotkey daemon that is launched as a systemd user service, you will have to restart it after this
- proper error handling
- delete systemd service unit afterwards (or have a respective setting) (is needed?, one approach is to keep an extra go process alive for every unit)
- ad hoc keybindings to change auxillary settings
- sometimes mod key does not work (due to skipping rendering passes on no user interaction?)
- add font
- support --tty and stream or stream from journal