Post Ac1PMsI8a3Ny3tEhkG by vidar@m.galaxybound.com
 (DIR) More posts by vidar@m.galaxybound.com
 (DIR) Post #Ac1PMm59fPR4nt7Fg0 by vidar@m.galaxybound.com
       2023-11-20T20:23:30Z
       
       1 likes, 0 repeats
       
       I am afraid I might just have to write my own X11 window manager.
       
 (DIR) Post #Ac1PMoKpI79xn4SnNg by vidar@m.galaxybound.com
       2023-11-20T21:02:19Z
       
       0 likes, 0 repeats
       
       As it turns out, the first step is to reconfigure things so I can run *without* a wm. Basically, ensure my wm isn't what's keeping the x session running. That's easy. Once that's done, since I already run sxhkd adding a keybinding to swap back and forth between an in progress wm and something working is easy....(Yes, I'm procrastinating again)
       
 (DIR) Post #Ac1PMqKBtRq7xgBJfU by vidar@m.galaxybound.com
       2023-11-20T21:22:09Z
       
       0 likes, 0 repeats
       
       Why *shouldn't* I have my own window manager?
       
 (DIR) Post #Ac1PMsI8a3Ny3tEhkG by vidar@m.galaxybound.com
       2023-11-21T05:21:48Z
       
       0 likes, 0 repeats
       
       It's tempting to basically just connect a DrB server to an X socket, so all the window management logic can be written in individual separate #Ruby scripts "client side". DrB makes Ruby server code extremely crash resistant (you can ensure any exceptions are forwarded to the client), and coupled with using sxhkd to handled the key and mouse events the amount of code is absolutely minimal.