Emmanuel Lepage Vallée

Well, the `request::activate` handler is meant to be disconnected and replaced by something that suits your needs. I am not convinced the default should change. In the past, doing those...

> What's the status of this PR? There will be another pull request after `ruled.client` gets merged to add permission granting/denying to the rules. This will be a much nicer...

Hello, Can you edit the following 2 files and post a screenshot of the result? This should regenerate the 2 images you see in the doc. https://github.com/awesomeWM/awesome/blob/master/tests/examples/wibox/widget/imagebox/horizontal_fit_policy.lua https://github.com/awesomeWM/awesome/blob/master/tests/examples/wibox/widget/imagebox/vertical_fit_policy.lua

> cover only really works if you set it on both vertical and horizontal policies In that case, there's probably some interaction with `valign` and `halign`. It might be worth...

I don't have that much time right now. Do you think you can do a pull request? You have all the context. A better alternative would be to implement the...

> However, I'm not sure if I ever saw anyone using that feature... My config uses it ;) You are probably right about **C**. It is the most intuitive outcome...

@fellowseb All for it! Please also note that there is a couple of interesting pull requests open to improve some aspects such as the performance. Someone who would tie all...

and btw one using the async APIs https://github.com/Elv13/awesome-configs/blob/master/customMenu/appmenu.lua

`id` are not unique. The API is like JavaScript. It returns a table with all the result for that `id`. The problem right now is that if you create widgets...

Honestly, I don't know. I made it this way so people coming from JavaScript don't have to learn anything new and make the wibox "DOM-like". This issue was reported twice...