In the following, I will go through my yabai and skhd setup and explain how it can replicate the classic i3wm behavior. Yabai and skhd to the Rescue!Īfter fiddling around for a few days, I’ve settled with a setup that works really well for me: yabai as a tiling window manager and skhd to define keyboard shortcuts that perform yabai (and some other) commands, replicating most of the functionality that is available in i3wm. While finding that (doom) Emacs worked basically out-of-the-box using the emacs-mac build ( brew tap railwaycat/emacsmacport brew install emacs-mac -with-modules) and my Zsh configuration was working without any major changes, finding a workable replacement for i3wm was a much harder task. Therefore, my first goal when switching to macOS was to replicate as much as possible of this exact workflow. My Linux workflow was mainly keyboard-driven, using i3wm as a tiling window manager, Emacs as a programming IDE and as a note-taking tool with Org mode and Org Roam, and basically living in the terminal. Therefore, I’ve decided to finally ditch Linux and give macOS a try.
After having less and less available time due to my research, constantly tinkering with my system was no longer an option. I’ve experienced issues with Bluetooth, audio sinks and sources, printers, and more on a daily to weekly basis. While more stable in general, even Fedora has its sharp edges here and there.
This has brought me to Fedora Linux about two years ago. ArchLinux has taught me more than anything else about the Linux world, its bleeding edge character, and the issues that come along with it. After using Linux for almost a decade, I’ve finally gotten annoyed at all the little hiccups and issues that arrive from time to time when working in Linux.
0 kommentar(er)
