Aire-One

> * Running the code in Xephyr with both `master` branch code and 4.3 tag (the former didn't reproduce the issue and the latter doesn't seem to support the code...

Technically, you don't have anything to learn about ldoc. The documentation is automatically built when you run `make` if you have ldoc installed on your system (I think it's even...

This isn't the response you are looking for, but it seems to be the correct behavior to me. When you have a fullscreen client, you don't have other client around...

In this regard : why do we have 3 states normal, active and inactive? I think titlebar buttons are toggles, hence they should have only 2 possible states : active...

Hello @chr-sa, First, I have successfully reproduced the bug. I have to admit that it was tricky, and I had to try multiple times to get it correctly. From my...

AFAIR, the "this library shouldn't use beautiful" comes from https://github.com/streetturtle/awesome-wm-widgets/issues/274. The main idea is that some well-known libraries like https://github.com/lcpz/lain and https://github.com/lcpz/awesome-copycats enforces a pattern where the user defines the...

This commit changed the widget `:buttons()` method to be a normal property. https://github.com/awesomeWM/awesome/commit/3d918258e2fefdb6696fa6c35150235144561c18 It means we should now use `widget.buttons = blah` instead of invoking a function. This change is,...

I did some investigation today. The `:buttons()` legacy method still exists, so Awesome backward compatibility is actually working. The issue here isn't from Awesome, but from the widget implementation. The...

(some wild guesses that need more investigations) I think the issue here is that xcb need a keycode to grab the keyuser event. In Awesome, we translate the symbol to...

EDIT: Oops sorry. I thought we were in the Awesome repository. Feel free to dismiss my comment. Hello @musjj, ~~This issue sounds unrelated to Awesome.~~ LGI (https://github.com/lgi-devs/lgi) is a Lua...