AEROSPACE-FOCUS(1)

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

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

okay so bestie, this is aerospace-focus from the AeroSpace manual, and it's literally all about moving your focus around. buckle up πŸŽ€

🌸 NAME 🌸

aerospace-focus β€” set focus to a window. that's it. that's the whole vibe check. πŸ’–

✨ SYNOPSIS ✨

aerospace focus [-h|--help] [--ignore-floating] [--wrap-around]
                [--boundaries <boundary>] [--boundaries-action <action>]
                [--fail-if-fullscreen] [--fail-if-macos-native-fullscreen]
                (left|down|up|right)
aerospace focus [-h|--help] [--ignore-floating] [--wrap-around]
                [--boundaries <boundary>] [--boundaries-action <action>]
                (dfs-next|dfs-prev)
aerospace focus [-h|--help] --window-id <window-id>
aerospace focus [-h|--help] --dfs-index <dfs-index>

like, four whole ways to do it. pick your fighter 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

Set focus to a window. literally the whole point. πŸ‘‘

now here's the tea: contrary to i3, the focus command doesn't have a separate argument for focusing floating windows. nope. from the focus command's perspective, floating windows are part of the tree. periodt.

so how does it figure out where a floating window lives? the floating window's parent container is determined as the smallest tiling container that contains the center of the floating window. the way that technique eliminates the need for an additional binding for floating windows? iconic. no cap.

this behavior can be disabled with the --ignore-floating flag, if you're feeling different πŸ’…

also, focus child|parent isn't supported, because the necessity of this operation is under the question. like, they literally link the receipt:

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

πŸŽ€ OPTIONS πŸŽ€

  • -h, --help β€” print help. classic. 🍼
  • --boundaries <boundary> β€” defines focus boundaries. <boundary> possible values: (workspace|all-monitors-outer-frame). the default is: workspace
  • --boundaries-action <action> β€” defines the behavior when requested to cross the <boundary>. <action> possible values: (stop|fail|wrap-around-the-workspace|wrap-around-all-monitors). the default is: stop
  • --wrap-around β€” an alias for --boundaries-action wrap-around-the-workspace. ⚠️ heads up bestie: this flag is incompatible with either --boundaries-action or --boundaries. don't try to run them together, it's giving chaos πŸ’€
  • --window-id <window-id> β€” focus the window with specified <window-id>. direct hit 🎯
  • --dfs-index <dfs-index> β€” focus window by its index, based on a depth-first search (DFS) of the window within the workspace tree. index is 0-based. so like, zero is the main character, one is next, etc ✨
  • --ignore-floating β€” don't perceive floating windows as part of the tree. it may be useful for more reliable scripting. ngl if you're scripting, this is your bestie 🫢
  • --fail-if-fullscreen β€” exit with non-zero code if the current target window is fullscreen by the fullscreen command. only compatible with (left|down|up|right). lowkey a guardrail 🚧
  • --fail-if-macos-native-fullscreen β€” exit with non-zero code if the current target window is in macOS native fullscreen. only compatible with (left|down|up|right). yes, the native kind, they're different things iykyk πŸ“

🌈 ARGUMENTS 🌈

  • (left|down|up|right) β€” set focus to the nearest window in the given direction. simple, clean, directional slay πŸ’…
  • (dfs-next|dfs-prev) β€” set focus to the window before or after the current window in the depth-first order (top-to-bottom and left-to-right) of windows in the current workspace tree. in this mode, --boundaries must be workspace (the default) and --boundaries-action can be set to one of (stop|fail|wrap-around-the-workspace). so like, don't get creative with the other boundary values here, it won't fly πŸ™ˆ

🧚 RESOURCES 🧚

go read the guide, it's a whole mood πŸ’œ

πŸ’€ BUGS πŸ’€

found a bug? bestie, report it here:

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

maintainers will move verified bugs to:

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

so like, post it in the discussions first, they'll do the moving. that's their job, not yours ✨

πŸ‘‘ 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 version of the AeroSpace manual was served up on 2026-07-16 β€” go forth and focus, you absolute icon πŸ’–πŸ¦‹πŸŽ€

πŸ“¦ where this page comes from