Daniel Hahler

> BTW, "don't apply rules on awesome.startup" seems technically impossible. This is what this issue is discussion. An option to enable skipping of rules on startup. I agree with the...

@ff2000 Sounds like a plan: awesome would connect to the D-Bus signal(s) and then emit one itself internally, e.g. `resume` (according to the already existing `startup`). Do you feel like...

I guess it's more on the C side, which would "just" need to hook into dbus and then emit the signal. The "system module" would be just a particular set...

For reference: https://www.freedesktop.org/wiki/Software/systemd/logind/

@psychon Yes, it works as expected! I could see the "before" message just before suspending, and the other then after/when resuming.

I am not sure, but I think having this functionality (the textclock updating it after resuming) in awesome by default makes sense.

@timroes We have this by now (via @Oblomov): https://github.com/awesomeWM/awesome/blob/2192e61f891c90420088863e52c9f8b7a924a716/lib/beautiful/xresources.lua#L91-L100 ([via](https://github.com/awesomeWM/awesome/commit/f22ef5014d956629c7d90749c6b9b07d491264d1)).

Are clients urgent by default after all? (sorry for being lazy/ignorant) If so the section should get fixed / extended instead I guess.

Yeah, so it's a misunderstanding. A good way to test/trigger this is `sleep 3; printf '\a'` in a terminal, then go to another tag (if your terminal is configured to...

> I prefer this code, which doesn't modify the original activate: It makes sense to use a new/separate function here in general. So the FAQ should be updated in this...