You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The goal is to run a condition (or test_cmd) to know if the listener should trigger or not.
Use case: Based on whether my laptop is plugged or on battery I want different behaviors and avoid putting that logic in the on-timeout and on-resume as tests.
Current workaround:
I prefix my on-resume and on-timeout commands:
However, it's not perfect: I don't want the on-resume to run if in between I've plugged/unplugged my laptop. In other words, if the on-timeout did not trigger because of condition, I don't want the on-resume to run at all.
The text was updated successfully, but these errors were encountered:
Bump. I was also just wondering how I would implement seperate behaviours for when my laptop is plugged in and when it is not.
Would love to also see battery-specific listener options, e.g. a direct setting for the condition that the laptop is not plugged in, or using a critical battery level as a secondary condition.
To elaborate on the latter: Hypridle would additionally trigger on-timeout if the battery is less than or equal to the critical value and the user is AFK. The system could then automatically suspend/hibernate/shutdown, given that the user is absent.
The goal is to run a
condition
(ortest_cmd
) to know if the listener should trigger or not.Use case: Based on whether my laptop is plugged or on battery I want different behaviors and avoid putting that logic in the
on-timeout
andon-resume
as tests.Current workaround:
I prefix my
on-resume
andon-timeout
commands:However, it's not perfect: I don't want the
on-resume
to run if in between I've plugged/unplugged my laptop. In other words, if theon-timeout
did not trigger because ofcondition
, I don't want theon-resume
to run at all.The text was updated successfully, but these errors were encountered: