Where Is the Vis Editor Config File?
Vis editor visrc.lua lookup order with themes, plugins and lexer folders.
Last updated
Vis reads one Lua file at startup with a fixed lookup order. An env override wins, then the binary folder, then XDG config, then system and share fallbacks. Most users only ever touch the XDG copy.
Support files branch off the same tree. Themes, plugins, lexers and snippets each get a subfolder. Selection happens through set commands inside the rc file.
Where Vis stores this, by platform
~/.config/vis/visrc.lua
Sourced once at startup for options and commands. Lookup runs env override, binary dir, XDG, system, share. Themes, plugins, lexers and snippets branch off the same tree.
~/.config/vis/visrc.lua
Same XDG and env override logic with POSIX paths.
Frequently asked questions
How do I back up Vis config?
Copy visrc.lua plus the themes, plugins, lexers and snippets folders with the editor closed. Restoring means putting them back and opening once to confirm options and theme load. The help command lists active paths at runtime.
How do I use a custom config location?
Set VIS_PATH to the folder holding your support files. It takes first priority in the lookup order. This is the tidy way to carry a config across machines or test setups.
Notice an outdated path? Let us know.