Skip to content
New issue

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 not working #3903

Open
micangl opened this issue Mar 15, 2024 · 4 comments
Open

urgent = false not working #3903

micangl opened this issue Mar 15, 2024 · 4 comments

Comments

@micangl
Copy link

micangl commented Mar 15, 2024

Output of 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:

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.

Expected result:

Firefox is spawned on tag 8, but the tag icon doesn't turn red (meaning that the client is not urgent).

@actionless
Copy link
Member

i think it's raise in this case, not urgent

@micangl
Copy link
Author

micangl commented Mar 16, 2024

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.

@actionless
Copy link
Member

i've tested - it indeed works in the rules but the same not working as spawn args

@Elv13
Copy link
Member

Elv13 commented Aug 20, 2024

this will require adding systemd cgroups support to fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants