dotfiles VS bspwm

https://github.com/mathiasbynens/dotfiles/blob/main/.macos

You might be interested in this: https://github.com/mathiasbynens/dotfiles/blob/main/.macos

I don't advise just running Mathias' config as is, but read through it and see if anything seems to be something you want in yours, make the changes, and save it somewhere for the next time you're setting up a Mac.

There's some stuff in there about speeding up certain animations (look for `# Speed up Mission Control animations`), and about not reordering "spaces" (desktops, full-screen apps, search for `# Don’t automatically rearrange Spaces based on most recent use`) based on use which I think may also affect cmd+tab ordering? Not sure, but it's a setting I always change anyway because the default doesn't make sense for power users.

About the trolling thing, sorry, I was genuinely not sure if you were arguing in good faith or just making stuff up, as most of the things you were saying were just plain incorrect or dishonest, from comparing desktop computer performance to low-powered laptops, to incorrect statements about features macOS truly excels at.

Another resource is the .macos script from Mathias Bynens' dotfiles, which is the repo from the person in the article who gave the method for uncovering such system settings.

initially borrowed from these dots and then tailored to my needs.

I added a PR to fix rsync, mosh, and some other tools, since they will be broken out of the box.

But it seems this project has fallen behind on PRs.

If you would like to have this fix, you can do this after cloning the repo:

  git clone https://github.com/mathiasbynens/dotfiles && cd dotfiles

Set some sane defaults for the OS. Browse through this script and pick and choose things that you may like.

https://github.com/mathiasbynens/dotfiles/blob/master/.macos https://blog.jiayu.co/2018/12/quickly-configuring-hot-corners-on-macos/

macos setup script by Mathias Bynens

The biggest QOL improvements imo are found in the approach to the user-facing API design.

Compare basic multi-monitor commands in something like bspwm[1] or yabai[2][3] to twms on Windows where this is typically handled transparently by directional `move` and `focus` commands understanding monitor boundaries.

Besides this, Whim has implemented a very functional ctrl+p style command palette which provides a great interface for more advanced on-the-fly/one-time window manager interactions.

With komorebi I think that having different border colours to indicate different types of containers is very helpful (one colour for single window stacks, a different colour for monocle containers, a different colour for stacks with multiple windows), as well as custom window-based work area offsets[4] (so if you have an ultrawide monitor with only a single window on a workspace, you can add offsets to the sides so it doesn't stretch across the whole width and give poor usability).

It's not really any one "big thing" but rather a difference in approach which adds up over many small design decisions.

[1]: https://github.com/baskerville/bspwm/issues/563

Bspwm is a window manager. Configuration happens in $XDG_CONFIG_HOME/bspwm/bspwmrc, as per stated here: https://github.com/baskerville/bspwm

Use BSPWM. It supports right clicks by default and its modular. You might want to look for status bars that work with it, slstatus does not work. Good luck, supremacist!

I had not heard of bspwm but I am a fan of telling WMs. Looking at the documentation now, I really like the pragmatic approach lol https://github.com/baskerville/bspwm

If you use the bspwm off of github instead of the old 0.9.10, you can use bspc node @parent -y next to cycle the split type of the parent of the focused. I added it ~1.5years ago, after baskerville added node -y horizontal and node -y vertical to set the split type of a node to vertical/horizontal ~2 years ago.

Also bspwm's JSON generation and parsing is not great. If you have a window with quotes in its class name, bspwm, when dumping it, will not escape them generating invalid JSON (e.g. {"className":"the "cool" window",) that jq will not be able to read, and even worse, bspwm itself will not be able to read. (Yes, if a window's class name contains a " character, bspwm will fail to reload after you run wm -r #1362).

Just follow this guide