Since this uses hyprlang, when I wrote my config I took the liberty to create variables for every command the listeners will run, only to realize variables declared inside the file cannot be used inside commands.
hypridle probably just takes everything after the = on things like on-timeout, on-resume, lock_cmd etc. as a string and makes the shell execute it without evaluating it at all, which makes it act differently than the way Hyprland can be configured, where (from what I can see) you can put variables in things that are meant to be executed.
I don't know if you care about this, but I figure someone is going to try doing this too, so it would be nice as a feature.
Since this uses hyprlang, when I wrote my config I took the liberty to create variables for every command the listeners will run, only to realize variables declared inside the file cannot be used inside commands.
For example, this:
does not work.
hypridle
probably just takes everything after the=
on things likeon-timeout
,on-resume
,lock_cmd
etc. as a string and makes the shell execute it without evaluating it at all, which makes it act differently than the way Hyprland can be configured, where (from what I can see) you can put variables in things that are meant to be executed.I don't know if you care about this, but I figure someone is going to try doing this too, so it would be nice as a feature.