AEROSPACE-MOVE(1)

πŸ“¦ version 0.21.3-Beta, in nixpkgs unstable

πŸ’… AEROSPACE-MOVE(1) β€” the AeroSpace manual, bestie edition ✨

okay so this is aerospace-move from the AeroSpace manual, and it's literally the glow-up your window layout has been waiting for 🫢


🌸 NAME 🌸

aerospace-move β€” move the focused window in the given direction. that's it, that's the whole vibe ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

aerospace move [-h|--help] [--window-id <window-id>] [--boundaries <boundary>]
               [--boundaries-action <boundary-action>] [--fail-if-fullscreen]
               [--fail-if-macos-native-fullscreen] (left|down|up|right)

πŸŽ€ DESCRIPTION πŸŽ€

So basically: you take the focused window and you move it in whatever direction you asked for. that's the whole thing πŸ’–

if you want to actually see it happening, the "Examples" section down there is where it's at β€” it's giving before-and-after makeover montage, no cap.

⚠️ deprecated name alert: move-through β€” that's the old name, it's still a thing but like, it's so last season. use move πŸ’…

✨ OPTIONS ✨

  • -h, --help β€” prints the help. classic, iconic, does exactly what it says on the tin πŸŽ€
  • --window-id <window-id> β€” instead of acting on the focused window, you point at a specific window. and the way this flag flexes? it takes precedence over the AEROSPACE_WINDOW_ID and AEROSPACE_WORKSPACE environment variables. main character energy fr fr πŸ‘‘
  • --boundaries <boundary> β€” sets where the moving has to stop, i.e. the move boundaries. possible values for <boundary>: (workspace|all-monitors-outer-frame). the default is: workspace.
  • --boundaries-action <boundary-action> β€” decides what happens when you're asked to move across the <boundary>. possible values for <boundary-action>: (stop|fail|create-implicit-container). the default is: create-implicit-container.
  • --fail-if-fullscreen β€” if the target window is fullscreen by the fullscreen command, it exits with a non-zero code. like, it's not doing it, and it's telling you so 😭
  • --fail-if-macos-native-fullscreen β€” same energy but for macOS native fullscreen: exits with a non-zero code if the target window is in macOS native fullscreen. πŸ™ˆ

πŸ”₯ EXAMPLES πŸ”₯

1. Given this layout

h_tiles
β”œβ”€β”€ window 1 (focused)
└── window 2

move right will result in the following layout

h_tiles
β”œβ”€β”€ window 2
└── window 1 (focused)

2. Given this layout

h_tiles
β”œβ”€β”€ window 1
β”œβ”€β”€ window 2 (focused)
└── v_tiles
    β”œβ”€β”€ window 3
    └── window 4

move right will result in the following layout

h_tiles
β”œβ”€β”€ window 1
└── v_tiles
    β”œβ”€β”€ window 3
    β”œβ”€β”€ window 2 (focused)
    └── window 4

3. Given this layout

h_tiles
β”œβ”€β”€ window 1
└── v_tiles
    β”œβ”€β”€ window 3
    β”œβ”€β”€ window 2 (focused)
    └── window 4

move left will result in the following layout

h_tiles
β”œβ”€β”€ window 1
β”œβ”€β”€ window 2 (focused)
└── v_tiles
    β”œβ”€β”€ window 3
    └── window 4

4. Implicit container example 🧚

sometimes move has to implicitly create a container to fulfill your command. it's not being dramatic, it's just doing what you asked πŸ’…

Given this layout

h_tiles
β”œβ”€β”€ window 1
β”œβ”€β”€ window 2 (focused)
└── window 3

move up will result in the following layout

v_tiles
β”œβ”€β”€ window 2 (focused)
└── h_tiles
    β”œβ”€β”€ window 1
    └── window 3

v_tiles is an implicitly created container. yes, it spawned a whole container out of thin air, slay πŸ¦‹

πŸ“Œ Remark: if --boundaries is set to all-monitors-outer-frame and there is a monitor in the up direction, the implicit container isn't created. Instead, window 2 would be moved to the monitor above the current. plot twist 🌈

πŸ’œ RESOURCES πŸ’œ


πŸ’€ BUGS πŸ’€

found a bug? bestie, report it here:

https://github.com/nikitabobko/AeroSpace/discussions/categories/potential-bugs

the maintainers will move verified bugs over to:

https://github.com/nikitabobko/AeroSpace/issues

(so yes, there's a whole pipeline. very organized. we love that for them πŸ‘‘)


🌸 LICENSE 🌸

Copyright Β© 2023 Nikita Bobko

Free use of this software is granted under the terms of the MIT License You can find the full text of AeroSpace license and its dependencies in the 'legal' directory of the distributed zip archive.


⭐ AUTHOR ⭐

Nikita Bobko and contributors


and that's the whole page, bestie 🫢 this was AeroSpace, dated 2026-07-16 β€” go forth and move some windows πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from