Emmanuel Lepage Vallée

I am not against, but there is some tiny risks of breaking some people. While `git grep -E '[(][a-z1-9]+[.]fit_widget'` returns nothing to worry about (code doing `function foo(a,b,c) if c...

The newer one seems a bit better https://awesomewm.org/apidoc/index.html The top image still has some resize issues in mobile form factor, but not the main table, at least not in Firefox.

Sorry for the ultra long delay, I finally got there is in my "things to look at queue". Looks like the fix is: ```lua client.connect_signal("request::activate", function(c) awful.ewmh.activate(c, context, { switch_to_tag...

@Aire-One What's your take on this? Should we close this PR? Or should we make a new variant of emit signal with the extra pcalls? There are definitively some places...

> swallowed error could silently run along and fail somewhere else, making debugging much harder. Right now, when we do this, we don't swallow the errors, the red popup with...

There's some news related to this. At least for now, there is a `[read only]` label in the doc https://awesomewm.org/apidoc/core_components/client.html

Some newer DE stopped caring about startup notification with the rise of Wayland. They now use SystemD CGroups to track from which origin a gui window comes from. Given the...

@raven2cz Thanks for the feature @Aire-One Mergify.io seems broken, it didn't see the PR and didn't auto merge it. This is the first time we had one which should have...

I think the issue is [here](https://github.com/Crylia/crylia-theme/blob/develop/awesome/src/tools/desktop_parser.lua#L33) (missing this `:close()`) rather than the file_readable call just above it.

Doing this cleanly will be some work, but it could be implemented: 1. Extend the drawin/wibox classes to be able to create "fake" clients. So AwesomeWM manages those as clients...