Setup Memory

[azr]

Howdy ! Big AeroSpace face here.

There is one thing that could be better which is that every time that I unplug my screens, everything is sent to random places. And it can happen a few times a week, you know grab your laptop to order groceries in the kitchen type of thing.

Anyways, it would be nice if I could 'save setup' in aerospace, and it'd save which program goes to which workspace, then I could 'restore setup' when I want and AeroSpace would put things back into their places.

Thanks!

[ELLIOTTCABLE]

I've got an existing thread on at least half of this - it's a very difficult problem to solve, thanks to how Apple handles displays:

#1159: Stable monitor assignment when there's multiple copies of the same monitor

I do intend to take another stab at the problem at some point; but it's also entirely possible that this is unsolvable without private APIs or really nasty hacks that Nikita won't want in AeroSpace (and rightly so.)

There's some small chance that if I A. do return to the problem, B. find a stable solution, and C. it's not acceptable to upstream, that I opt to maintain a small fork with that janky fix (because I'm in your boat with the "constantly changing display layout" being my biggest continuous pain-point w/ AeroSpace.)

---

As for the non-display-arrangement/monitor-unplugging saving of a setup, I would also love that, although it's a much lower priority for me, personally. The current approach everyone's taking, as nasty as it is, is a big pile of on-window-detected callbacks with specific commands to try and jimmy them into the right places in some sort of stable/repeatable way (for me, there's about ~10 windows I need to arrange every time I boot my machine, sigh.) It definitely would be nice to have a slightly different approach to this - although personally instead of dynamically 'saving' whatever the current-on-screen-state is, I think it'd be more in the vein of AeroSpace's design to have a better textual-UI in the config for declaring entire multi-window/multi-app "layouts" that are pre-defined, in a declarative instead of imperative way.

There's lots of threads on that, as well (particularly see #1911 Declarative layouts from a couple weeks ago.)