A community-driven vim distribution
This is a list of the frequently asked questions about SpaceVim.
The SpaceVim install script will move your
~/.vimrc_back. If you want to have a try SpaceVim without
overwriting 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. This introduced a lot of problems.
When loading a Vim file the file content is executed line by line. This means that when there was an error the content
before the error was still executed. This led to unforeseen problems.
We decided going forward to use a more robust configuration mechanism in SpaceVim. SpaceVim must be able to load the whole configuration file and if there are syntax errors in the configuration file, the entire configuration needs to be discarded.
We compared TOML, YAML, XML, and JSON. We chose TOML as the default configuration language. Here are some of the drawbacks we found with the other choices considered:
SpaceVim loads custom global configuration from
~/.SpaceVim.d/init.toml. It also supports 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 uses true colors, so you should make sure your terminal supports true colors. This is an article about what true colors are and which terminals support true colors.
Sometimes you will see
Updating failed, The plugin dir is dirty. Since the plugin dir is a git repo, if the
directory is dirty (has changes that haven’t been committed to git) 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 git documentation.
In Neovim we can use
g:python3_host_prog to config python prog. 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 introduce two new environment variables:
export PYTHON_HOST_PROG='/home/q/envs/neovim2/bin/python' export PYTHON3_HOST_PROG='/home/q/envs/neovim3/bin/python'
This is a feature of terminal emulators. You can use
Ctrl-q to unfreeze Vim. To disable
this feature you need the following in either
Hosted on GitHub, Help improve this page — Theme by mattgraham,