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.
