Where Does Xed Store Settings?
Xed keeps settings in dconf under org.x.editor on Linux, with preference branches for editor, UI, print and encodings. No config file exists.
Last updated
Xed is the Mint editor that never wrote a config file. All behavior sits in dconf under the org.x.editor schema family, from editor preferences through interface and print down to window state. Forum threads confirm the absence rather than just failing to find it.
That makes backup a dconf operation and nothing else. Dump the tree, move machines, load it back. Plugin and style homes stay unquoted here because no source pins them down, which is itself useful to know before going hunting.
Where Xed stores this, by platform
/org/x/editor
Root settings tree with verified children for editor, UI, print, encodings, window state and plugins. Inspect with gsettings list-recursively. Backing store defaults to the shared dconf user database.
Frequently asked questions
How do I back up Xed settings?
Dump the editor branch with dconf dump and restore with dconf load. The root schema covers preferences for editor behavior, interface, printing and encodings plus window state and plugins. One user report confirms no equivalent of a geany.conf exists anywhere.
How do I stop Xed restoring cursor position?
Set it through the preferences editor schema key for restoring cursor position. The Mint forums document that exact gsettings call, which is the clearest proof the dconf tree is authoritative. No text file alternative backs it.
Where do Xed plugins live?
They could not be verified. Plugin locations, style paths and accelerator maps have no documented home, so this post quotes none of them. The settings tree below is the verified part. Anything deeper would be guessing.
Notice an outdated path? Let us know.