Editora 0.19.0 docs. You are reading an archived version, kept so links from that release keep working. Read the 0.21.0 docs →

Configuration

Editora keeps preferences and session state in a config folder. Most settings have a UI in the Settings window; everything underneath is plain text you can edit by hand.

Config directory

The folder is chosen by this precedence:

Source	Location
`--config-dir <path>` (CLI)	that path
`EDITORA_CONFIG_DIR` (env var)	that path
`--dev` flag	`~/.editora-dev/`
default	`~/.editora/`

~ is your home directory; on Windows that is %USERPROFILE%, so the default folder is %USERPROFILE%\.editora.

Use --dev to run a development instance that never touches your everyday settings or session. The live path is shown in About Editora. See the command-line reference for all the flags.

Files

File	Holds
`settings.json`	Preferences: font, theme, keymap, tab size, view options, auto-save, keybinding overrides
`workspace-state.json`	Session: open files, folds, tool-window layout, window geometry
`recent-files.json`	Recent files list
`projects.json` + `projects/<id>.json`	Project index and each project’s session
`bookmarks.json`	Bookmarks (per project)
`notes.json`	Personal notes (per project)
`breakpoints.json`	Debugger breakpoints (per project)
`connections.json`	Saved SFTP connections (no secrets)
`plugins.json` + `plugins/<id>/`	Enabled plugins and their folders
`dictionary.txt`	Your added spell-check words
`macros.json`	Saved keyboard macros
`abbreviations.json`	Your abbreviations
`trusted-folders.json`	Folders you have trusted to run their build wrappers
`snippets/<lang>.json`, `templates/*.json`	Your snippets and file templates

Preferences, sessions, and list files are JSON. If settings.json is absent, Editora converts an existing settings.toml automatically and removes the old file only after the JSON replacement has been written safely.

Inside a project

Two files live in the project itself rather than in your config directory, so they can be committed and shared:

File	Holds
`.editora/settings.json`	Toolchain overrides for this project: which language server to run for a language, and whether to run it
`.editora/run-configurations.json`	Run configurations exported for the team

Only toolchain settings can be overridden this way; appearance, keymap and fonts stay personal, because checking out a repository should not rearrange somebody else’s editor. Project: Edit Project Settings… creates the first file with an example. An existing project TOML file remains readable and is converted when you open Edit Project Settings. See projects.

Preferences (settings.json)

Edit in the Settings window, or directly:

{
  "fontFamily": "JetBrains Mono",
  "fontSize": 14,
  "theme": "Editora Dark",
  "tabSize": 4,
  "autoSave": "afterDelay"
}

autoSave accepts off, afterDelay, or onFocusChange. Text zoom is stored separately as fontZoom (adjusted with C-= / C-- / C-0 or Ctrl+wheel) and isn’t shown in the Settings window.

Schema versioning

Each structured config file carries a schemaVersion. Editora migrates older files forward automatically on read. A file written by a newer Editora than you’re running is backed up to <name>.v<n>.bak and defaults are loaded, so an older build never clobbers a newer config.

Export and reset

Export Configuration… (Settings → Advanced, or config.export) zips the active config folder into a timestamped archive in your home directory. Local history, .bak backups, and installed plugins are included. Runtime files are not: downloaded language servers and debug adapters, jdtls workspaces, the instance lock, the MCP endpoint file with its live token, and the session log.
Reset to Defaults (Settings → Advanced) resets every preference, including the keymap choice, which goes back to Emacs. Text zoom is kept, and your key rebinds stay stored with the keymap you made them in, so they apply again when you switch back to it.

Keymaps and rebinding: Keymaps & keybindings.
Themes, fonts, and zoom: Themes & fonts.
Snippets and templates: Snippets & templates.

Full internals live in the README.