I’ve finally installed #Niri. After 20+ years using #dwm, #wmii, #i3wm, #sway, I was skeptical but it just “clicked”!

All other tiling window managers I’ve tried work great but require a lot of configuration and fine-tuning. Niri feels like the obvious way to handle windows right from the beginning. Amazing UX.

Hidden bonus: it’s not yet compatible with #XWayland. A solution is under way, but right now it gets you rid of all Electron apps. 🙃

https://github.com/YaLTeR/niri

GitHub - YaLTeR/niri: A scrollable-tiling Wayland compositor.

A scrollable-tiling Wayland compositor. Contribute to YaLTeR/niri development by creating an account on GitHub.

GitHub

A few years ago I did a quick analysis of my #Bash histfile and horrified my coworkers that `#git rebase` was my most frequently used command.

It's not on top, but It's still in the top 10. (I think gitk getting so much higher up is that with #Emacs #EXWM I loose track of windows more than I did with #WMII, so I just open a new one, and end up with 15 open gitk windows before I realize this and run `killall wish`).

(HISTSIZE is set to 50,000 commands, which comes out to about 8 months)

Наконец-то я успокоился. Поставил себе на ноутбук Bunsenlabs, поскольку очень нравится Crunchbang Linux. Также поставил wmii, переделал его конфигурацию, чтобы походила на исходный Bunsenlabs - и все, доволен. Даже несмотря на то, что не удалось приладить имена к тегам, но я думаю, что наверно кто-то подскажет (возможно), но в целом некритично.
#linux #bunsenlabs #wmii
I really miss #wmii 's ability to send windows to several workspaces in #i3wm sometimes.

i barely used #wmii's #9p interface, back in the day. but i think i need to go back & live in that world for a little bit. re-experience it, & learn the interface, see how it worked. ideally do a couple #streams walking through it a little. to inform my web-shell interests. cross the recent #TabFS greatness.

i 'd love to find a good discussion on what i3 (window manager improved improved improved) changed, in their core architecture, as they forked/rebuild wmii. why i3? what happened there? did the desire for a new custom text protocol drive that change? or was that incidental? what about the core ui was different to users?