skhd VS i3

It exists! Check out [yabai](https://github.com/koekeishiya/yabai), which is nicely paired with [skhd](https://github.com/koekeishiya/skhd).

I have a 49 inch CRG9 and the best recommendation for window management is Yabai (https://github.com/koekeishiya/yabai) along with skhd (https://github.com/koekeishiya/skhd). Yabai is a greedy window management solution that tries to fit opened applications in given space and skhd let's you easily jump between those using keyboard shortcuts. This has massively improved my ultrawide experience.

Only disclaimer is, configuring yabai has a slight learning curve.

I want to echo this as well. I use a 2nd tool to help me add additional i3-like keyboard shortcuts as well (I have the ability to "stack" windows with Alt-S and rotate through them with Alt-J and Alt-K).

It's called skhd https://github.com/koekeishiya/skhd

I forgot where the script for the stacking is. I can look that up separately, but I'm on mobile atm.

Try rcmd or skhd.

What I've done is configure yabai and skhd in a way that somewhat mimics my i3 setup (dotfiles in case it helps) with the help of Karabiner-Elements since Apple wouldn't recognize my keyboard layout properly (or at all...).

I use NixOS+GNOME+pop-shell for tiling windows on Linux, and I love it!

I am quite frequently on MacOS, and I use Yabai[0] and skhd[1], managed with Nix-Darwin for tiling windows and custom keyboard shortcuts. With how I make my Linux and MacOS builds look and feel identical it's pretty easy for me to forget when I'm on one vs the other.

For anyone curious, here's my repository for deploying my configs[3]. It's awesome to have one source of truth for managing NixOS servers and workstations, MacOS workstations, and other Linux workstations with Nix installed.

[0] https://github.com/koekeishiya/yabai

[1] https://github.com/koekeishiya/skhd

[2] http://daiderd.com/nix-darwin/

[3] https://github.com/heywoodlh/nixos-configs

You can install skhd with brew install skhd, and configure it by writing the following lines inside ~/.skhdrc:

I personally use skhd for binding hotkeys to multiple terminal commands. BetterTouchTool can also chain multiple commands, but I find it harder to edit than in an UI, depends on what you're comfortable with.

That, combined with skhd (for script hotkeys) and my rcmd app (for app switching) gave me a much better solution than the hard to edit config I had in Karabiner.

While I believe Memory Saver was a great improvement, it only works if the tab is hidden or the window minimized. I recently learned the required state is not triggered if the tab is open but on another virtual desktop. At least this is the case with many of not all Linux window managers. Some of the many discussion threads on the topic:

https://github.com/i3/i3/issues/4353

> This is very true, and unfortunately there are very few people working on linux accessibility (including not me! I am part of the problem!).

Accessibility work itself ironically suffers from an accessibility problem. I brought up i3wm above, the issue for that is pretty illuminating: https://github.com/i3/i3/issues/3393

It's not that the devs are saying "this doesn't matter", the devs behind one of the most popular tiling window managers in the X11 ecosystem are saying, "this does matter, but we don't know how to fix it. We don't know what changes we'd need to make to get Orca working."

It's a really fundamental breakdown that's kind of a tragedy because I honestly believe that if accessibility communities were more heavily baked into testing and development in Linux and if this wasn't treated like two separate worlds, it would be better for everyone -- fixing accessibility concerns very often improves interfaces across the board and makes them more powerful.

But... how do you bridge that gap? I don't really know, I tried looking into Orca to see what would need to happen here and bounced off of it pretty hard, it's not a very approachable tech stack and there aren't tutorials or getting started guides. And on the other side of the issue I can preach about needing accessibility input during interface design, but I'm not in a position to give specific advice because I don't use screenreaders or alternate control schemes and I don't know what the biggest problems are.

The people who need to be involved in that process can't get involved because there's a tech barrier in place even for technically inclined people, and because the underlying software locks them out from the start. i3wm isn't ever going to get someone who's intimately familiar with Orca to jump into the conversation because the people who need to use Orca can't use i3wm. So that leaves the people who can address that tech barrier, but they don't know what to do or how to approach the problem because of the lack of involvement and because the communities are isolated from each other. So it's a chicken-and-egg problem and I don't know how to solve it.

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I use MacBook Pro (Retina, 15-inch, Mid-2014) with Manjaro as OS using i3 as a window manager. It isn't perfect, but I'm thrilled with it. I have been a Mac OS user for the last 15 years and wouldn't change what I have now for a Mac OS because I don't need more than what I'm using for development.

Even though, we have moved the official i3 support channel to GitHub discussions, i3's biggest community is still on reddit and if things continue like that there is going to be a lot of helpful content on an increasingly closed platform.

for example, take i3. https://github.com/i3/i3/issues/4478

For daily usage I really like kubuntu with i3wm, but it takes some configuration and getting used to the shortcuts, but it's well worth it