Where Does SpaceVim Store Config Files?
SpaceVim install dir, user init.toml and cache folders on every desktop OS.
Last updated
SpaceVim keeps one install dir driving both Vim and Neovim. User settings live separately in a SpaceVim.d folder as init.toml. No editor native config file is owned by the distribution.
Plugin blobs and merged configs land in cache. An env var relocates the user dir. Project folders can overlay their own copy for local tweaks.
Where SpaceVim stores this, by platform
~/.SpaceVim.d/init.toml
Default user config in TOML. Install dir re-clones from upstream. Cache holds merged plugin configs. Relocatable via env var. Project-local overlay possible.
~/.SpaceVim.d/init.toml
Same install plus user dir split with POSIX paths.
%USERPROFILE%\.SpaceVim.d\init.toml
Same layout under the user profile. Install updates through the bundled script.
Frequently asked questions
How do I back up SpaceVim?
Copy the SpaceVim.d folder with editors closed. The install dir re-clones from upstream. Restoring means putting SpaceVim.d back and pulling the install to match.
How do project-local configs work?
Drop an init.toml in a SpaceVim.d folder inside the project. It joins runtimepath for that project only. Global settings stay in the home copy.
Notice an outdated path? Let us know.