2 ms·
Sway was the reason why I moved back from Wayland to X (and started to use XMonad on my main machines). While I was using Sway, I realized that I really like ti
by not_your_vase 3y ago
Sway was the reason why I moved back from Wayland to X (and started to use XMonad on my main machines). While I was using Sway, I realized that I really like tiling WMs, but I also really disliked some of the annoying bugs and idiosyncrasies of it (and of wlroots). I still use it as the base of one of my pet projects due to its excellent IPC protocol, but I switched away from it for actual work.
- jauntywundrkind 3y agoI've never heard any complaints like this? Do you have examples? Are there open issues? My experience has been that Sway is utterly reliable.
- not_your_vase 3y agoThe most annoying thing that ultimately ended my relation is that frequently there are multiple focused windows: 1 that is displayed as focused, and 1 that actually receives the input from the keyboard (I do set a thick red border around the active window on all my WMs to always). I have no idea what triggers it, but every 20-30 minutes I found myself staring at the screen thinking why my text is not showing up in the active window, just to find it in a window that I have switched away a long time ago. And my pet-peeve: virtual keyboards don't work with Qt when using wlroots (at least not the activation events). I managed to add the missing protocol in a private fork, but I found it a glaring omission.
- jauntywundrkind 3y agoI've never seen this or understand it, but +1 up vote for the report. Godspeed.