A community-driven vim distribution
this is a list of most asked questions about SpaceVim.
The install script of SpaceVim will move your
~/.vimrc_back. If you want to have a try with SpaceVim without overwrite
your own vim configuration. you can clone SpaceVim manually.
git clone https://github.com/SpaceVim/SpaceVim.git ~/.SpaceVim
then, start vim via
vim -u ~/.SpaceVim/vimrc. you can also put this alias into your bashrc.
alias svim='vim -u ~/.SpaceVim/vimrc'
In the old version of SpaceVim, we used a vim file (
init.vim) for configuration. But this introduced a lot of problems. When loading the vim file the file content is executed line by line. That means if there is an error then the content before the error also will be executed. This will lead to unforeseen problems.
So we’re going to use a more robust way to configure SpaceVim. SpaceVim will be able to load the whole configuration file; if there are syntax errors in the configuration file, the entire configuration will be discarded.
After comparing TOML, YAML, XML, and JSON, we chose TOML as the default configuration language.
The yaml file is parsed into json and cached in the cache folder, and when SpaceVim is started again, the configuration file inside the cache is read directly
SpaceVim load custom global configuration from
~/.SpaceVim.d/init.toml. It also support project specific configuration,
That means it will load
.SpaceVim.d/init.toml from the root of your project.
The problem was git auto added ^M when cloning, solved by:
git config --global core.autocrlf input
By default, SpaceVim use true colors, so you should make sure your terminal support true colors, This is an articl about what is true colors and the terminals which support true colors.
Sometimes you will see
Updating failed, The plugin dir is dirty. Since the dir of a plugin is a git repo, if the
directory is dirty, you can not use
git pull to update plugin. To fix this issue, just move your cursor to the
error line, and press
gf, then run
git reset --hard HEAD or
git checkout .. for more info, please read
documentation of git.
In neovim we can use
g:python3_host_prog to config python prog. but in SpaceVim
the custom configuration file is loaded after SpaceVim core code. so in SpaceVim itself, if we using
:py command, it may cause errors.
so we intrude two new environment variable:
export PYTHON_HOST_PROG='/home/q/envs/neovim2/bin/python' export PYTHON3_HOST_PROG='/home/q/envs/neovim3/bin/python'
Hosted on GitHub, Help improve this page — Theme by mattgraham,