hm... somewhere along the way, the inhibit functionality broke ^^;;
turns out that the watch command needs a terminal connected to it, and the TERM env variable to be set (see https://unix.stackexchange.com/questions/17999/how-can-i-run-watch-as-a-background-job).
not sure why it worked before all the refactoring honestly... but this should be a better approach anyways I think
netbrain
commented
2 months ago
hm... somewhere along the way, the inhibit functionality broke ^^;; turns out that the
watchcommand needs a terminal connected to it, and theTERMenv variable to be set (see https://unix.stackexchange.com/questions/17999/how-can-i-run-watch-as-a-background-job). not sure why it worked before all the refactoring honestly... but this should be a better approach anyways I think