Workspace 10 when using external monitor

[megasuperlexa]

Sometimes when I plug in my external monitor, workspace 10 appears. I did not configure it, so it is inaccessible via shortcuts.

my config:

# See: https://nikitabobko.github.io/AeroSpace/commands#workspace
alt-1 = 'workspace 1 --auto-back-and-forth'
alt-2 = 'workspace 2 --auto-back-and-forth'
alt-3 = 'workspace 3 --auto-back-and-forth'
alt-4 = 'workspace 4 --auto-back-and-forth'
alt-5 = 'workspace 5 --auto-back-and-forth'
alt-6 = 'workspace 6 --auto-back-and-forth'
alt-7 = 'workspace 7 --auto-back-and-forth'
alt-8 = 'workspace 8 --auto-back-and-forth'
alt-9 = 'workspace 9 --auto-back-and-forth'
alt-0 = 'workspace 0 --auto-back-and-forth'
ctrl-alt-right = 'workspace next --wrap-around'
ctrl-alt-left = 'workspace prev --wrap-around'

[nikitabobko]

It's by design. 10 is a phantom workspace. As soon as it's no longer visible and doesn't contain windows, it will disappear by itself.

To make 10 "invisible" you can manually move one of your workspaces to the newly connected monitor

AeroSpace uses the "phantom workspace" approach because out of your configured workspaces which particular one should be moved to the newly connected monitor? What if you didn't have enough of configured workspaces?

[megasuperlexa]

in my case there are empty workspaces 4-9, I expected Aerospace to use one of these

[nikitabobko]

one of these

Again, which particular one? And why this particular one but not another? These questions are rhetorical, there is no good answer

I want the workspace to monitor assignment to be explicit and predictable. If I didn't move the workspace to another monitor then it shouldn't move