THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Emmanuel Lepage Vallee (Elv13)
Attached to Project - awesome
Summary - c.screen change on ctrl+mod4+r
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - Hi,
Here is a little test I did to see why some client screen after restart broke
somewhere in the last 2 weeks.
At line 1 of the "manage" rc.lua hook (the default one, directly from git)
print("manage",c.name,c.screen)
And a similar print in awful.tag.withcurrent()
When I move a client to screen 2, I see the withcurrent print saying it is now
on screen 2. Good!
But when I restart awesome, I see c.screen = 1. Until recently, when awesome
restarted, c.screen were kept. I think it is a pretty bad regression. I know
there is some valid use case for changing the screen, but it should not be the
default.
More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1243
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.
