2018-01-31 14:59:29 +08:00
|
|
|
---
|
|
|
|
|
title: "FAQ"
|
|
|
|
|
description: "A list of latest blog about the feature of SpaceVim and tutorials of using vim."
|
|
|
|
|
---
|
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.
|
|
|
|
|
|
|
|
|
|
## Where should I put my configration?
|
|
|
|
|
|
|
|
|
|
SpaceVim load custom global configuration from `~/.SpaceVim.d/init.vim`. It also support project specific configration,
|
|
|
|
|
That means it will load `.SpaceVim.d/init.vim` from the root of your project.
|
|
|
|
|
|
|
|
|
|
## 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
|
|
|
|
|
|
|
|
## Why SpaceVim can not display default colorscheme?
|
|
|
|
|
|
|
|
|
|
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.
|
