← All features

Run configurations

Save how a thing is launched — Java main class, Python or shell script, or a make target — with a before-launch build step, a toolbar selector, and a file you can commit so your team gets the same ones.

Run configurations in Editora

A run configuration is a saved answer to “how is this launched”: the main class or script, program and VM arguments, environment variables and a working directory. Pick one in the toolbar and hit Run or Debug, with Stop beside them; the choice is remembered across restarts.

Four kinds, not just Java

Choose a Type in Settings → Run Configurations:

Script configurations need no project and no language server at all. Debugging remains Java-only, and says so rather than reporting a confusing Java error.

A step before the launch

A configuration can name a command to run first — a build, a codegen step. A non-zero exit aborts the launch, so a stale binary is never run by accident.

Shareable

Export Configurations to Project writes them to .editora/run-configurations.json inside the project, where they can be committed alongside per-project settings. Import merges them back by name, so importing twice doesn’t duplicate and a colleague’s edit updates the configuration rather than doubling it.

It stays out of your way