We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
urgent = false
Output of awesome --version:
awesome --version
awesome v4.3 (Too long) • Compiled against Lua 5.3.6 (running with Lua 5.3) • D-Bus support: ✔ • execinfo support: ✔ • xcb-randr version: 1.6 • LGI version: 0.9.2
How to reproduce the issue:
Launch client which supports the startup notification protocol with awful.spawn, whilst setting the urgent property to false:
awful.spawn
urgent
false
awesome-client 'require("awful.spawn").spawn("firefox", { urgent = false, tag = "8" })'
Actual result:
Firefox is spawned on tag 8 - as expected - but the tag icon still turns red, thus indicating that the client's urgent property must be true.
true
Expected result:
Firefox is spawned on tag 8, but the tag icon doesn't turn red (meaning that the client is not urgent).
The text was updated successfully, but these errors were encountered:
i think it's raise in this case, not urgent
raise
Sorry, something went wrong.
I've tried swapping urgent with raise, hence running
awesome-client 'require("awful.spawn").spawn("firefox", { raise = false, tag = "8" })'
Unfortunately, it didn't work.
i've tested - it indeed works in the rules but the same not working as spawn args
rules
this will require adding systemd cgroups support to fix
No branches or pull requests
Output of
awesome --version
:How to reproduce the issue:
Launch client which supports the startup notification protocol with
awful.spawn
, whilst setting theurgent
property tofalse
:awesome-client 'require("awful.spawn").spawn("firefox", { urgent = false, tag = "8" })'
Actual result:
Firefox is spawned on tag 8 - as expected - but the tag icon still turns red, thus indicating that the client's
urgent
property must betrue
.Expected result:
Firefox is spawned on tag 8, but the tag icon doesn't turn red (meaning that the client is not
urgent
).The text was updated successfully, but these errors were encountered: