2018-01-31 14:59:29 +08:00
|
|
|
---
|
|
|
|
|
title: "FAQ"
|
2018-05-12 19:01:00 +08:00
|
|
|
description: "A list of questions and answers relating to SpaceVim, especially one most asked in SpaceVim community"
|
2018-01-31 14:59:29 +08:00
|
|
|
---
|
2017-10-28 14:57:02 +08:00
|
|
|
|
2018-01-31 14:59:29 +08:00
|
|
|
# SpaceVim FAQ
|
2017-11-13 17:14:19 +08:00
|
|
|
|
2018-01-31 14:59:29 +08:00
|
|
|
this is a list of most asked questions about SpaceVim.
|
|
|
|
|
|
2018-02-22 10:05:04 +08:00
|
|
|
<!-- vim-markdown-toc GFM -->
|
|
|
|
|
|
2018-03-31 18:42:03 +08:00
|
|
|
- [Where should I put my configuration?](#where-should-i-put-my-configuration)
|
2018-02-22 10:05:04 +08:00
|
|
|
- [E492: Not an editor command: ^M](#e492-not-an-editor-command-m)
|
|
|
|
|
- [Why SpaceVim can not display default colorscheme?](#why-spacevim-can-not-display-default-colorscheme)
|
|
|
|
|
- [Why I can not update plugins?](#why-i-can-not-update-plugins)
|
|
|
|
|
|
|
|
|
|
<!-- vim-markdown-toc -->
|
|
|
|
|
|
2018-05-13 12:59:41 +08:00
|
|
|
## Where should I put my configuration?
|
2018-01-31 14:59:29 +08:00
|
|
|
|
2018-05-13 12:59:41 +08:00
|
|
|
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.
|
2018-01-31 14:59:29 +08:00
|
|
|
|
2018-05-13 12:59:41 +08:00
|
|
|
## E492: Not an editor command: ^M
|
2017-11-13 17:14:19 +08:00
|
|
|
|
|
|
|
|
The problem was git auto added ^M when cloning, solved by:
|
|
|
|
|
|
|
|
|
|
```sh
|
|
|
|
|
git config --global core.autocrlf input
|
|
|
|
|
```
|
2018-01-31 14:59:29 +08:00
|
|
|
|
2018-05-13 12:59:41 +08:00
|
|
|
## Why SpaceVim can not display default colorscheme?
|
2018-01-31 14:59:29 +08:00
|
|
|
|
|
|
|
|
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.
|
2018-02-22 10:05:04 +08:00
|
|
|
|
2018-05-13 12:59:41 +08:00
|
|
|
## Why I can not update plugins?
|
2018-02-22 10:05:04 +08:00
|
|
|
|
2018-05-13 12:59:41 +08:00
|
|
|
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.
|
