[awesome bugs] #1310 - Current client gets tagged as urgent and mod4+u does not move to next urgent
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1310 - Current client gets tagged as urgent and mod4+u does not move to next urgent User who did this - Daniel Hahler (blueyed) -- This can be closed, the PR has been merged: https://github.com/awesomeWM/awesome/pull/60 But not for 3.5.x. -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1310#comment4220 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1310 - Current client gets tagged as urgent and mod4+u does not move to next urgent
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1310 - Current client gets tagged as urgent and mod4+u does not move to next urgent User who did this - Daniel Hahler (blueyed) -- The other improvement mentioned is provided in https://github.com/awesomeWM/awesome/pull/33/. -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1310#comment4185 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1310 - Current client gets tagged as urgent and mod4+u does not move to next urgent
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1310 - Current client gets tagged as urgent and mod4+u does not move to next urgent User who did this - Daniel Hahler (blueyed) -- TEST CASE: 1. two terminals 2. in the first one: sleep 5 ; echo ^G 3. go to the second one: sleep 1; echo ^G (use ^V^G to get the actual bell control character) Now the second (current) client got tagged urgent last. With the PR, mod4+u will do nothing on first invocation, but moves to the other client on second invocation. Without the PR, mod4+u will never move away from the current client. -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1310#comment4184 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1310 - Current client gets tagged as urgent and mod4+u does not move to next urgent
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#1310 - Current client gets tagged as urgent and mod4+u does not move to next urgent User who did this - Daniel Hahler (blueyed) -- I have added a PR for this: https://github.com/awesomeWM/awesome/pull/60 This will remove the urgent state also on the current client. Another improvement to this might be that the focused client would not receive the urgent flag in the first place? -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1310#comment4183 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
[awesome bugs] #1310 - Current client gets tagged as urgent and mod4+u does not move to next urgent
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. A new Flyspray task has been opened. Details are below. User who did this - Daniel Hahler (blueyed) Attached to Project - awesome Summary - Current client gets tagged as urgent and mod4+u does not move to next urgent Task Type - Bug Report Category - Core Status - Unconfirmed Assigned To - Operating System - All Severity - Low Priority - Normal Reported Version - git/master Due in Version - Undecided Due Date - Undecided Details - Sometimes it happens that the current client gets tagged as urgent, and I cannot switch to another urgent client (on another tag) using mod4+u (awful.client.urgent.jumpto). I need to switch to another client then (mod4+j) before I can switch to the other urgent client. After mod4+j I see that the previous client is displayed as urgent for a short time, but then this state gets removed (it shortly is displayed as red in the taskbar). It looks like: a) the current client should not get marked as urgent b) mod4+u should remove the urgent flag also on the current client Using (older) Git master. I've updated it now - maybe it got fixed by the latest commits already. More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1310 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
