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:

SourceLocation
--config-dir <path> (CLI)that path
EDITORA_CONFIG_DIR (env var)that path
--dev flag~/.editora-dev/
default~/.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

FileHolds
settings.tomlPreferences: font, theme, keymap, tab size, view options, auto-save, keybinding overrides
workspace-state.jsonSession: open files, folds, tool-window layout, window geometry
recent-files.jsonRecent files list
projects.json + projects/<id>.jsonProject index and each project’s session
bookmarks.jsonBookmarks (per project)
notes.jsonPersonal notes (per project)
breakpoints.jsonDebugger breakpoints (per project)
connections.jsonSaved SFTP connections (no secrets)
plugins.json + plugins/<id>/Enabled plugins and their folders
dictionary.txtYour added spell-check words
snippets/<lang>.json, templates/*.jsonYour snippets and file templates

Preferences are TOML; session and list files are JSON.

Preferences (settings.toml)

Edit in the Settings window, or directly:

fontFamily = "JetBrains Mono"
fontSize = 14
theme = "Primer 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

More

Full internals live in the README.