12 issues in kernc/xsuspender
Fixes https://github.com/kernc/xsuspender/issues/10. Additionally, define _DEFAULT_SOURCE to adhere to BSD signal semantics. See manual signal(2) § Portabilty for info.
Assertion failed, probably at/after system resume from suspend: ERROR: xsuspender.c:138:xsus_window_suspend: assertion failed: (! xsus_entry_find_for_window_rule (window, rule, suspended_entries)) Xsuspender ...
Issue When opening a new chromium window if chromium is suspended it does not get opened until i focus one of existing chromium windows. This is a bit annoying, but additionally window gets spawned on ...
Fixes #3. Use pgrep from procps. The change avoids all other dependencies (bash, awk, coreutils, findutils). Other approaches (e.g. libprocps or parsing /proc) aren't portable.
Issue Currently window matchers only accept exact match. So that means if window class is chromium-browser, match_wm_class_contains = chromium would only match chromium window class and not chromium-browser ...
Implement configuration reloading by sending SIGUSR1 to xsuspender. This enables if xsuspender is started without process supervision to still be able to reload config without restarting it.
Idea Implement a scripts that checks whether suspension is needed or not based on current process behavior. Have an option which scripts to activate for a profile. Example checks - Does application ...
Issue description Currently it's possible to specify exec_suspend command that gets executed when suspend is triggered. While user can override the suspension process, he needs to re-implement process ...
Issue description Currently procps, gawk, coreutils, bash and findutils are needed to run a script that suspends whole process tree. This not only presents extra unneeded dependencies, but also slows ...