Hi there, I just want to put something up for discussion: not to add a systray in the default config or keep the line with the systray commented out, because it can lead to an entirely unstartable awesome. The reason is that when awesome's rc.lua has runtime errors awesome falls back to default rc.lua while keeping the things done in the user's rc.lua executed to the point of failure (which can result in two taglists, for example, when crashing here I often see mine and the default one). But that could also mean that the user's rc.lua has created a systray and because of a coding error the default rc.lua is executed as fallback, creating a second systray, which results (at least with me) in a total quit of awesome*. Because I just use the .xinitrc with startx to start the X-Server with awesome X quits after awesome quits, taking all started X-applications down with it (which it of course doesn't do if awesome just restarts, then everything is still there), including the editor the configuration is potentially modified in (annoying when it falls back to commandline an you have vim or sth. like that, but I don't know if there might be a scenario where you might have a real problem with a not-starting awesome). After I realized why awesome was going down that far, because the second systray is created in the default configuration, I commented it out there to avoid this behavior for the future, which works quite well. So, because already a little negligence at the wrong point, which I think happens from time to time to most of us, can cause this annoyance, I want to propose to modify the default rc.lua that way.
Feel free to comment this idea! Cheers Manuel *) Error: "/usr/share/awesome/lib/wibox/widget/systray.lua:60: More than one systray created!" -- To unsubscribe, send mail to [email protected].
