Skip to content

Settings

  • MUST. Opened by Ctrl/Cmd+, and a palette command. A sidebar of pages with icons on the left, the page on the right, and a search field on top.
  • Search finds a row by its title, description, visible text, its card or section heading, its page name and English keywords. Title hits rank above description hits; whole words above word starts. The page with the best match opens, and every non-matching row, heading and card is hidden (SettingsSearch).
  • Live apply. No Save button. Text fields commit on Enter or focus loss; invalid numbers are marked and never committed.
  • A change made in one window reaches every other open window.
Editora's Settings window searching for sync, with the Sync page open
Typing sync in Settings: pages without a match grey out and the best page opens.
  1. Model field, default and accessors, with a schema bump and migration.
  2. Control, built once, writing the field and applying it.
  3. Row on its page with search keywords.
  4. Load line that sets the control from the model, safe to run at any time.
  5. Palette command that flips or prompts the same field, plus strings in every catalog.
  • Config lives in ~/.<app> (~/.<app>-dev for --dev, any folder via --config-dir or <APP>_CONFIG_DIR).
  • settings.json for preferences, workspace-state.json for session state, other stores in their own JSON files.
  • Every versioned file has a SCHEMA_VERSION and a v → v+1 migration step. A purely additive field uses an identity step.
  • A file newer than the running build is backed up to <name>.v<n>.bak and defaults load: an older build never clobbers a newer config.
  • Export configuration writes a timestamped .zip of the config folder (ConfigExporter). Import restores from one.
  • SHOULD. Optional sync of settings, keybindings and user data through a Git repository the user owns.
  • Setup by pasting a repo URL, or Create on GitHub through the gh CLI. The account that can read the repo is pinned per clone, so machines with two GitHub accounts work.
  • Automatic (on change and at start) and manual triggers. Machine-local keys (window size, paths) never sync.
  • Conflict rule: on a same-entry conflict this machine wins. A backup is taken before any sync that replaces local files.
  • Status shows as a pill in Settings and as echo messages; failures go to the Message Log.
  • Reference: sync/SyncEngine, sync/SyncMerge, sync/SyncAccount, ui/SettingsSync, docs/subsystems/settings-sync.md.
Editora's Sync settings page
Editora's Sync page: repository, branch, Create on GitHub… and what to sync.
Torrenta's Sync settings page
Torrenta's Sync page.
Termina's Sync settings page
Termina's Sync page.

Version 1.0.0 · · Changelog