Scoria

Settings

Ctrl + , (app:open-settings) opens Settings. Every value in it is read from your vault's .obsidian folder, so what you see is your real configuration rather than a set of Scoria defaults.

Warning

Settings is read-only. A banner at the top of the window says so. Nothing you see can be changed from inside Scoria; to change a setting, change it in Obsidian or edit the JSON in .obsidian/ directly. This is deliberate: Obsidian rewrites an entire settings file on every change, and doing that safely — without dropping keys Scoria does not know about — belongs with the round-trip gate rather than ahead of it.

The tabs

TabRead from
Generalapp.json
Appearanceappearance.json
Interfaceapp.json, appearance.json
Editorapp.json
Files and linksapp.json
Hotkeyshotkeys.json, over the command registry
Core pluginscore-plugins.json
Community pluginscommunity-plugins.json and each plugin's manifest.json
Quick switcherswitcher.json
Command palettecommand-palette.json

The last two are plugin tabs, and appear the way Obsidian shows a core plugin's own options tab.

Each row is drawn as Obsidian draws it: a name, a description, and a control showing the current state. The layout and the wording follow Obsidian 1.14.4.

Which settings actually do something

Showing a setting and honoring it are different things, and the distinction matters. These are the ones that change how Scoria behaves:

SettingKeyEffect
Default view for new tabsdefaultViewModeWhether a note opens in reading view or editing
Live PreviewlivePreviewWhich editing mode a note opens in
Strict line breaksstrictLineBreaksWhether a single newline is a line break
Readable line lengthreadableLineLengthSoft wrap width while editing
Indent using tabs / Tab sizeuseTab, tabSizeWhat Tab inserts in a list
Smart list indentationsmartIndentListWhether Enter continues a list
New link formatnewLinkFormatThe path shape of a rewritten link
Use [[Wikilinks]]useMarkdownLinksThe form of links Scoria creates
Automatically update internal linksalwaysUpdateLinksWhether a rename rewrites links without asking
Default location for new notesnewFileLocation, newFileFolderPathWhere a new note lands
Deleted filestrashOptionSystem trash, .trash/, or outright
Confirm file deletionpromptDeleteWhether deleting asks
Detect all file extensionsshowUnsupportedFilesWhether unknown kinds appear in Files
Base theme, accent colortheme, accentColorThe window's colors
Fonts and font sizeinterfaceFontFamily, textFontFamily, monospaceFontFamily, baseFontSizeTypography

Settings that are shown but not yet acted on include spellcheck, auto-pairing of brackets and Markdown, Vim mode, inline title, fold heading and fold indent, line numbers, indent guides, right-to-left, and cssTheme. They are read from your configuration and displayed truthfully; the behavior behind them is not implemented.

Core and community plugins

The Core plugins tab shows which of Obsidian's core plugins your vault has enabled, reading both the modern map shape and the legacy array shape of core-plugins.json. Scoria implements the core plugins as part of the application rather than as separate modules, so the tab is informational: switching one off in Obsidian does not currently remove the corresponding pane from Scoria.

The Community plugins tab lists your installed plugins, read from community-plugins.json and each plugin's manifest — name, version, author, description.

Note

Community plugins are listed, not run. They are JavaScript written against an Electron application; Scoria is a native binary and cannot execute them. A native plugin interface of Scoria's own is the last planned phase. See Obsidian compatibility.

Not shown

Some settings are absent rather than disabled, because the specification does not yet record the app.json key behind them — and inventing a key would be worse than omitting the row. These include: the default file to open, deleting attachments with their note, Mermaid support, quick font-size adjustment, zoom level, window frame style, and URI callbacks. Obsidian's Keychain tab, and the options tabs of core plugins other than the quick switcher and the command palette, are also not shown.

Unknown keys are safe

Every config reader carries unrecognised keys through untouched. A setting written by a newer Obsidian than the specification covers is read, kept, and still there afterwards — which is only meaningful because Scoria does not rewrite these files at all today, and is the property that has to hold before it does.

Next

Source: sites/scoria/content/docs/settings.md