On 2013–01–21 Andre Klärner wrote: > > I don't know how other window managers deal with this issue. Do they > > all completely lose the state and fall back to the default window > > configuration? > > Well, I for my part also had the problem that the state got lost, but I was > also annoyed by the fact, that on each boot (and my work-machine has to be > powered on and off each day) I have to start all applications again and > move them to the right tag, and so on. So I looked around and found rules > and shifty.
Rules are a very powerful tool that I appreciate since my first day of using awesome. They are great for setting up static and predictable applications such as web browser, IRC client, mail reader, etc. However, they are only usable if the setup can be expressed as a rule (this applied to shifty as well, since shifty is also driven by rules). One problem you already mentioned yourself: some things are hard or impossible to express as a rule. Awesome allows for manual adjustment of tiling layout, window proportions (mwfact), number of master windows, etc. If everything could be expressed as a rule these functions would not be necessary. Tagging clients manually would also be superfluous. Yet, there is a reason that all these adjustments can be done manually and people use it for good reasons. And it's exactly those settings that get lost when awesome restarts, those settings that can't be expressed by rules because they were set up during the work flow, like your VLC or virtualbox setup. Rules can surely reduce the mess created during a restart, but they don't solve the foundational problem of forgetting the state. Marco
signature.asc
Description: Digital signature
