Emmanuel Lepage Vallée

Can you check with `bustle` is the action is indeed taken rather than this being something else? Also, do you use the legacy notification module or the new one (aka,...

I merged the PR, please update and retry

It was a known problem when I wrote that doc. The reason why I did it this way is because AwesomeWM delegates the image loading to GDK/Cairo. They have multiple...

This would require to strip out the window management code from the "other" processes (and most of `capi`). It might also be easier to do share-nothing threads within the main...

Hello, Thanks for this. I think there is multiple ways to implement this feature. I think the most trivial would be to expose `:raise()` and `:lower()` for the wiboxes and...

So lets start with the parts we all agree on. 1) the problem is real, 2) it is worth fixing, 3) the current layering code is confusing. I made a...

Here you go https://github.com/elv13/collision * Select clients by direction * Move clients by direction * Move floating clients by relative offset * Select screens by direction * Select tag by...

In that case it would be `swap_by_direction`, but it has some issues and isn't such a good idea because of floating vs. tiled clients. If you implement a trivial swap...

Ah, yeah, we could have that one. I always wanted to add move iterators and navigation methods to the screens to handle geometric navigation and iteration (from left to right,...

It is in `gears.geometry.rectangle.get_in_direction`. However given the rarely changing screen layouts, it may be worth it to cache the result and daisy-chain the screens (internally, in Lua). Then add `myscreen.left/right/up/down`...