feat: SIGUSR2 handling for toggles, wayland enigo feature
#281
+119
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds:
SIGUSR2to handy to toggle recording on and off,waylandfeature toenigoExample usage of SIGUSR2 (Sway config):
Now, whenever I press
alt+o, it'll toggle on, and I press it again, it toggles off. Easy.(
pkillis used here but it doesn't actually "kill" anything. It's just sending that signal to the process matching the name "handy", which we handle!)Complications
Enabling the
waylandfeature on enigo seems to affect the overlay monitor detection (only inside of wayland). Just using X11 detection actually works (at least in Sway), but by using the wayland detection, enigo instead early-errors out with:This seems like an upstream bug which needs to be fixed to properly gracefully fallback.