Gaze/SpaceVim
1
0
Fork 0
mirror of https://github.com/SpaceVim/SpaceVim.git synced 2025-01-23 12:50:04 +08:00
Code Issues Projects Releases Wiki Activity

Fix typo: configration -> configuration

Browse Source
This commit is contained in:
Miguel Madrid Mencía 2018-03-31 12:42:03 +02:00
parent fde0c3fec8
commit d9547cf232
No known key found for this signature in database
GPG Key ID: 4D0F6894D41C6957
3 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
autoload/SpaceVim.vim
View File

@ -579,7 +579,7 @@ function! SpaceVim#loadCustomConfig() abort
exe 'source ' . custom_glob_conf
endif
else
call SpaceVim#logger#info('Skip glob configration of SpaceVim')
call SpaceVim#logger#info('Skip glob configuration of SpaceVim')
endif
elseif filereadable(custom_glob_conf)
if isdirectory(expand('~/.SpaceVim.d/'))

8
docs/documentation.md
View File

@ -191,7 +191,7 @@ This section is an overview of layers. A more extensive introduction to writing
**Purpose**
Layers help collect related packages together to provide features. For example, the `lang#python` layer provides auto-completion, syntax checking, and REPL support for python files. This approach helps keep configuration organized and reduces overhead for the user by keeping them from having to think about what packages to install. To install all the `python` features the user has just to add the `lang#python` layer to their custom configration file.
Layers help collect related packages together to provide features. For example, the `lang#python` layer provides auto-completion, syntax checking, and REPL support for python files. This approach helps keep configuration organized and reduces overhead for the user by keeping them from having to think about what packages to install. To install all the `python` features the user has just to add the `lang#python` layer to their custom configuration file.
**Structure**
@ -282,7 +282,7 @@ let g:spacevim_guifont = 'DejaVu\ Sans\ Mono\ for\ Powerline\ 11'
Comprehensive documentation is available for each layer by <kbd>:h SpaceVim</kbd>.
if you want to add custom `SPC` prefix key bindings, you can add this to SpaceVim configration file, **be sure** the key bindings is not used in SpaceVim.
if you want to add custom `SPC` prefix key bindings, you can add this to SpaceVim configuration file, **be sure** the key bindings is not used in SpaceVim.
```vim
call SpaceVim#custom#SPCGroupName(['G'], '+TestGroup')
@ -453,7 +453,7 @@ all the colors based on the current colorscheme
**Statusline separators:**
It is possible to easily customize the statusline separator by setting the `g:spacevim_statusline_separator` variable in your custom configration file and then redraw the statusline. For instance if you want to set back the separator to the well-known arrow separator add the following snippet to your configuration file:
It is possible to easily customize the statusline separator by setting the `g:spacevim_statusline_separator` variable in your custom configuration file and then redraw the statusline. For instance if you want to set back the separator to the well-known arrow separator add the following snippet to your configuration file:
```vim
let g:spacevim_statusline_separator = 'arrow'
@ -528,7 +528,7 @@ endfunction
this example is for gruvbox colorscheme, if you want to use same colors when
switch between different colorschemes, you may need to set
`g:spacevim_custom_color_palette` in your custom configration file. for example:
`g:spacevim_custom_color_palette` in your custom configuration file. for example:
```vim
let g:spacevim_custom_color_palette = [

6
docs/faq.md
View File

@ -10,16 +10,16 @@ this is a list of most asked questions about SpaceVim.
<!-- vim-markdown-toc GFM -->
- [Where should I put my configration?](#where-should-i-put-my-configration)
- [Where should I put my configuration?](#where-should-i-put-my-configuration)
- [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 -->
### Where should I put my configration?
### Where should I put my configuration?
SpaceVim load custom global configuration from `~/.SpaceVim.d/init.vim`. It also support project specific configration,
SpaceVim load custom global configuration from `~/.SpaceVim.d/init.vim`. It also support project specific configuration,
That means it will load `.SpaceVim.d/init.vim` from the root of your project.
### E492: Not an editor command: ^M