72
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 08 Jul 2023
72 points (91.9% liked)
Asklemmy
43940 readers
472 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
Sway for going on 2 years I think. I do recommend it, and Wayland/tiling wms in general.
I use my own fork that uses bspwm-style "long-side split by default," and a nearly transparent under-the-hood container-squashing refactor that prevents this behavior from causing the tree to become bloated with invisible nodes and start to lag horribly. The fix won't be accepted in Sway since it's the bug is faithfully reproduced from i3, and I haven't had time to rewrite it for i3. But if you use something like sway-autotiling, you've probably noticed the issue.