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
Thanks for this tool, very useful for my case where external HDMI hotplug events are not being reported by udev for some reason...
I would like to be able to temporarily, then permanently disable the portion of your code that does not react to duplicate events. In my testing with hotplug/unplug my external HDMI, I get debug messages such as,
xplugd[2470]: Same message as last time, time 73277688, skipping ...
Could you add a flag to allow reaction to duplicate events instead of skipping them? Perhaps with a sub-argument with a cool down period in seconds? So, xplugd -d 3 would react to any event it thinks is a duplicate, as long as the duplicate was at least 3 seconds in the past?
The text was updated successfully, but these errors were encountered:
Sorry mate, i'm not using xplugd myself anymore. Maybe I'll get back to using it in the future. I can review and merge pull requests though, if you or someone else find the time to fix it yourself.
Thanks for this tool, very useful for my case where external HDMI hotplug events are not being reported by udev for some reason...
I would like to be able to temporarily, then permanently disable the portion of your code that does not react to duplicate events. In my testing with hotplug/unplug my external HDMI, I get debug messages such as,
xplugd[2470]: Same message as last time, time 73277688, skipping ...
Could you add a flag to allow reaction to duplicate events instead of skipping them? Perhaps with a sub-argument with a cool down period in seconds? So, xplugd -d 3 would react to any event it thinks is a duplicate, as long as the duplicate was at least 3 seconds in the past?
The text was updated successfully, but these errors were encountered: