Aire-One

I don't think we need an itest here. A unit test should be enough. We need to use a spy to mock and observe the `awful.spawn` invokation (http://olivinelabs.com/busted/#spies-mocks-stubs). @Ancker-0 these...

Every utility functions from `awful.spawn` is based of on calling `awesome.spawn`. Basically, `awful.spawn` is an abstraction over `awesome.spawn`. You can use a table argument to "truncate" your command with `awful.spawn`....

Since we now introduced flexbox in our CSS for the mouse style list, I think we could also use it to stack the two UML table for smaller screens. I'll...

> After the screen indices are swapped the list signal is emitted causing layout.arrange in lib/awful/layout/init.lua to run. I'm still trying to understand what this function does (will update). Layout.arrange...

> should we make a new variant of emit signal with the extra pcalls? No, it wouldn't solve the initial issue. > And I really don't think this should be...

AFAIK, client icon_name property is readonly in our API. (As identified by the issue https://github.com/awesomeWM/awesome/issues/3457, we indeed need to explicitly show this flag in the documentation) > Unfortunately c.icon_name is...

> actually after reading the spec for both WM_NAME and WM_ICON_NAME i dont see a reason why one of them is readonly and other is not - i think we...

> > 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 > > @Elv13 whats the difference between apidoc...

Hello, that's not a feature we currently have, and it looks like there isn't many interest in it. I guess the best option you have is to implement this behavior...

Oh! Guess I'm wrong, your PR just made me realize there is a possible workaround: You can change the layout skip_gap function to implement the desired behavior. This would however...