Hi there,
seems the names got mixed up in the patch :)
hook.py
-------
def startup_once(self, func):
return self._subscribe("startup", func)
def startup(self, func):
return self._subscribe("restart", func)
manager.py
-----------
if not no_spawn:
hook.fire("startup_once")
hook.fire("startup")
Cheers,
Niklas
On 21.09.2014 23:37, Tycho Andersen wrote:
On Sun, Sep 21, 2014 at 04:27:57PM -0300, Roger Duran wrote:
On Sun, Sep 21, 2014 at 1:56 PM, Tycho Andersen <[email protected]> wrote:
Hi all,
We are thinking of changing the startup hook slightly. A quick survey
of the configs in qtile-examples shows that almost /everyone/ has
logic in their config to make sure the startup hook only spawns
programs once. This is much better done in qtile proper, I think. I
still think it would be useful to have a hook that runs on every qtile
start. To that end, I've prepared the following patch:
https://github.com/tych0/qtile/commit/0ed4be038e6f59058cc0108f646c4fc29ee7144e
The only question is what to call this new hook. I called it
"restart", but I'm not entirely sure that is the best name for it :).
Feedback welcome, silence is tacit acceptance and I will push this
patch in a few days if I don't hear from anyone.
As i said on irc, what about startup and startup_once?
That's fine with me. Anyone else have any thoughts?
\t
--
You received this message because you are subscribed to the Google Groups
"qtile-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"qtile-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
