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 - Make rules aware of "startup" / global startup variable?
Task Type - Feature Request
Category - Lua libraries
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Normal
Reported Version - git/master
Due in Version - Undecided
Due Date - Undecided
Details - It might be useful to have the "startup" state (which indicates that 
the rules are applied during startup) available in the rules callback.

awful.rules connects to the manage signal, but does not use/forward the startup 
argument.

I could only imagine that there was a global variable, which could be used to 
get that information.

(I know that you could manually add a signal handler to track this, but this is 
inconvenient).

More information can be found at the following URL:
https://awesome.naquadah.org/bugs/index.php?do=details&task_id=1222

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.

Reply via email to