creating-hammerspoon-scripts

Use hs.window.focusedWindow() to get the active window, then call win:setFrame() with coordinates derived from screen:frame(). Bind the function to a hotkey with hs.hotkey.bind(), and always check that the focused window is not nil before manipulating it.

Call hs.hotkey.bind() with a modifier table like {"cmd", "alt"}, a key name, and a callback function. For multi-step workflows, use hs.hotkey.modal.new() to create a modal mode, and always call modal:exit() after each action.

Watchers stored in local variables get garbage collected by Lua once init.lua finishes executing. Store every watcher (pathwatcher, wifi, application, USB) in a global variable by removing the local keyword so it persists for the session.

Hammerspoon only reads init.lua at launch or on explicit reload via hs.reload(). Add a reload hotkey or set up an hs.pathwatcher on ~/.hammerspoon/ that calls hs.reload() automatically when Lua files change.

Yes, Hammerspoon supports multi-monitor setups on macOS 11.0+. Use win:screen():next() to get the next display and win:moveToScreen() to move the window, and use screen:frame() rather than fullFrame() to avoid the menubar and dock.