Question 1

How do I set up a basic window management script in Phoenix?

Accepted Answer

Create a ~/.phoenix.js file and use the Window API to define functions for moving or resizing windows, then bind them to keyboard shortcuts with Key handlers. Refer to the documentation for starter examples.

Question 2

Phoenix vs Hammerspoon: which is better for macOS automation?

Accepted Answer

Phoenix is lighter and uses JavaScript, ideal for minimalists familiar with JS. Hammerspoon uses Lua and has a larger ecosystem with more built-in modules. Choose based on your scripting preference and need for community support.

Question 3

Can I run shell commands from Phoenix scripts?

Accepted Answer

Yes, Phoenix allows executing external commands directly from JavaScript using its API, similar to running commands in the terminal. This is listed as a key feature for automation tasks.

Question 4

How to debug errors in my Phoenix configuration?

Accepted Answer

Use the log() function to output messages to the console or enable debug mode with ~/.phoenix.debug.js. Check system logs and the documentation for troubleshooting common scripting issues.

Question 5

Does Phoenix work with multiple monitors?

Accepted Answer

Yes, Phoenix provides Screen and Space APIs to manage windows across multiple monitors programmatically. You can script layouts and movements based on screen coordinates and properties.

Question 6

Is Phoenix safe to use with accessibility permissions?

Accepted Answer

Phoenix requires accessibility permissions to control UI elements, which is standard for automation tools. It's open-source, so you can audit the code, but always grant such permissions cautiously to trusted apps.

Phoenix

What is Phoenix?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions