AEROSPACE-RUN-CALLBACK(1)

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

πŸ’… AEROSPACE-RUN-CALLBACK(1) β€” the AeroSpace Manual era πŸ¦‹

okay so bestie, this is aerospace-run-callback from the AeroSpace manual, and honestly? it's giving "let me press the button myself" energy. it runs your AeroSpace config callbacks on demand. periodt ✨


πŸŽ€ NAME

aerospace-run-callback β€” run AeroSpace config callbacks on demand 🫢

✨ SYNOPSIS

aerospace run-callback [-h|--help] [--for-every-window|--window-id <window-id>] on-window-detected
aerospace run-callback [-h|--help] (on-focus-changed|on-focused-monitor-changed)

like, that's literally the whole shape of it. two forms, pick your fighter 🌸

πŸ’– DESCRIPTION

Run AeroSpace config callbacks on demand πŸ’…

so normally AeroSpace fires these callbacks all by itself when events happen. this command is your little rewind button πŸ”₯ β€” you get to manually re-run the callbacks:

  • on-window-detected β€” the callbacks defined by the on-window-detected config option. by default they only run for the focused window, ngl. pass --for-every-window if you want the callbacks to hit every currently known window β€” truly iconic right after reload-config, so your new rules retroactively apply to windows that were already open πŸͺŸβœ¨ β€” or pass --window-id to target one specific window.
  • on-focus-changed β€” runs the commands listed under the on-focus-changed config key. simple. slay. πŸ’œ
  • on-focused-monitor-changed β€” runs the commands listed under the on-focused-monitor-changed config key. monitor main character energy πŸ‘‘

and here's the cute part: the command forwards stdout and stderr of all commands run in the callback πŸ˜­πŸ’– which opens up one more usecase β€” you can literally use this command to see the output of your callbacks. debugging but make it a vibe check πŸ”

🌈 OPTIONS

  • -h, --help β€” print help. classic. we love a helpful queen πŸŽ€
  • --for-every-window β€” run on-window-detected callbacks for every window. only valid with on-window-detected, and it's mutually exclusive with --window-id 🚫 β€” you can't have both, bestie, pick one.
  • --window-id <window-id> β€” act on the specified window instead of the focused window. this flag takes precedence over the AEROSPACE_WINDOW_ID and AEROSPACE_WORKSPACE environment variables πŸ‘‘ (yes, it wins, no cap).

only valid with on-window-detected. mutually exclusive with --for-every-window. again: one or the other 🫢

πŸ¦‹ ARGUMENTS

  • <callback> β€” one of: on-window-detected, on-focus-changed, on-focused-monitor-changed

literally just type one of those three. that's it. that's the argument πŸ’…

πŸ’€ EXIT CODES

the command forwards the exit code of the callback. whatever the callback did, that's what you get back β€” no filter, fr fr πŸ“€

🌟 RESOURCES

go read the guide, i'm begging 🧚

πŸ™ˆ BUGS

found a bug? report it to https://github.com/nikitabobko/AeroSpace/discussions/categories/potential-bugs πŸ›

the maintainers will move verified bugs to https://github.com/nikitabobko/AeroSpace/issues β€” so it's like a whole glow-up pipeline for your bug report ✨

πŸ‘‘ 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 β€” AeroSpace manual, dated 2026-07-16, brought to you with love (and zero chill) πŸ’…πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from