On 21.01.2013 12:26, Marco wrote:
I don't know the internals and the reasons behind this restart. How
likely is it that this issue will be fixed and what does it take to
fix it?
Well, look at your config. What do you see? For example, it takes the number of
screens and creates tags for these screen. So fixing this requires at least
another config break which is something that I'd like to avoid in the near future.
Now the internal reason:
When awesome starts, it creates a screen object for each screen and only later
does things with the rc.lua. So a screen can uniquely be identified by its index
in some array and the C core does this a lot.
Now imagine that screens can appear and disappear freely. We now have to
properly clean up behind old screens and make sure that nothing still refers to
it, else we get random crashes. This means some non-trivial amount of work is
involved. It's doable, but other stuff is more important.
Uli
--
To unsubscribe, send mail to [email protected].
