Aire-One

Wibar doesn't currently handle automatic resize based on its content length. You'll have to keep track of the size of the content manually and size the wibar manually when the...

That's an interesting finding @sclu1034! I'll update the labels accordingly. > You have several options: > > - Decrease the timeout to a value where the garbage collector at its...

> btw, what is this? (the ()) > > is there a difference between wibox.layout.fixed.horizontal and wibox.layout.fixed.horizontal()? Let's say : no, there is no difference for the end-user. The long...

Hello, it seems to work as expected in my computer. Spawning xterm gave me the following snid `"awesome/xterm/39887-0-lapew_TIME19538582"`, so setting the `c.startup_id` didn't fail since the string is not nil......

Hello, I only skim-read the issue, from what I get, it's about screen configuration that awesome doesn't handle as expected... We had a big refactor of the screen handling. So...

@mphe any update on the tests?

Everything is green. I'll give a chance to Mergify for automatic merge

Hello, That's actually a "nice to have" improvement! The titlebar buttons builder function already sets default tooltips with the button name : https://github.com/awesomeWM/awesome/blob/7451c6952e0a24bd54edc0f7ecff6ad46ef65dcb/lib/awful/titlebar.lua#L758-L761 I think it shouldn't be too hard...

In addition to unit tests, I'd like to also see examples to show the difference between all the layout modes. That's probably not something we want to ask for this...

Looks like the CI doesn't pass, all "Build & Test" jobs fail with: ``` 55 tests finished. There were 1 errors: - /home/runner/work/awesome/awesome/tests/test-awful-widget-only_on_screen.lua: Error: running function for step 4/20 (@1):...