03:12 <daurnimator> leon-p: it does in terms of crashes, updates and tool universality: e.g. can I use 2 different tagging programs in combination? where does that shared state live? do I have to provide permanent storage for the tagging engine? vs does it run as a daemon and keep in memory

03:15 <leon-p> crashes are bugs and as such should be fixed, not worked around. no you can't use two programs for tagging, because a single client will have full control over all window management, regardless of where the state lives. permanent storage of client data is a client-side problem: write it to a file if you must.

03:18 <leon-p> this won't be much different from X11 window managers implementing workspaces: the X server has no idea what is going on, it just maps and unmaps windows based on requests of the WM.

03:19 <leon-p> there are many /many/ problems with the X11 WM model, but this is not one of them

03:20 <leon-p> also keeping tag state in river would enforce those tags as the only possible workspace / tags / window grouping mechanism. however it's the explicit goal to allow for more flexibility in that regard

03:22 <leon-p> right now river always feels like river, no matter what layout you use. but the end goal is to have no such river "identity", but rather (pluggable) desktops build upon river as a stable but discrete base.

07:59 <dagle> Is there a way to make a window fullscreen and still being able to change window (or anything of that kind?). Because if a window creates a child popup window, the whole program becomes unusable and I have to toggle fullscreen and then toggle back.

13:17 <tleydxdy[m]> you might be looking for monocle mode