Emmanuel Lepage Vallée

Ok, I updated the description, if you have an idea of what has to be (technically) done, feel free to elaborate, you know XCB better than me

Sorry, I forgot to answer this one yesterday. > So, just allow a "random name" to be given as the name of the selection? Can't be more generic than that....

> Huh? Why would one need a special API for this? Can't that be implemented ontop of some "low-level" API. And no, I do not know of any tricks to...

> Besides this "might be too slow", any other comments on this API idea? It would be a good start. Also, it's hard to see the exact API until it...

They are called `button::press` and `button::release` and seem to be documented as such https://awesomewm.org/apidoc/core_components/client.html#button::press Can you clarify where in the doc it is stated otherwise?

@alfunx Mind creating a pull request to add `delayed_placement`? This is the sanest solution. Moving placement higher in the chain could cause issues. The `size_hints`, `titlebar` and `floating` are already...

> I think adding delayed (default false) key to the placement table could also be considered. Especially since using both placement and delayed_placement doesn't really make sense, I think. Yes,...

@dyfrgi Do you still plan to work on the test? As @actionless said, this is better done using an integration test suite since it has a full event loop and...

As @psychon mentionned, the order is intentional. tl;dr, as already mentionned, the rules are applied only once after all rules sources are "consulted". This is also on purpose to avoid...

Ah nice! This has been in my TODO list for years. Can you share this so I can use it in Tyrannical? AwesomeWM 4.3 have an half assed attempt done...