Emmanuel Lepage Vallée
Emmanuel Lepage Vallée
> It's odd since this only happens when running awesome. It's not odd. Awesome is the only WM without a built-in compositor to use ARGB surfaces by default. It stresses...
> if I try to load an invalid config Invalid or just a config containing a deadlock? Because that's not really the same type of issue.
Wasn't this about not having robot messages in regular PRs (even if the second link make no sense related to that issue)?
> Also, I had the impression that Elv13 wants people to upgrade to the latest version of awesome instead of staying with older, more-or-less-working versions That's your idea ;) You...
I think it would break exiting features such as transparent titlebars, client side shadows or generic "I have a compositor and I want to push it" cases. Also, if there...
> Well use ARGB "as needed" means if say the titlebar is transparent, awesome should use ARGB. Even if we added code to detect such situation (aka: add complexity), it...
this will require adding systemd cgroups support to fix
Thanks for this. Sorry for the delay, I didn't have time for Awesome over the last year and built a huge backlog of things to look at.
Sorry for the delay, I don't have a lot of time for Awesome right now. Won't think break people who add transparent titlebars or use anti-aliased round corners?
@yshui Maybe deprecate `--no-argb` and add a `--argb-mode=` where `on` remains the default? \* `ondemand` and not `auto` because `auto` would imply it detects when it really needs it, which...