I'm trying to configure my spacevim using init.vim instead of init.toml. I was wondering tho how can I set the layers options tho.

For example I wanted to change the shell position to be at the bottom instead at the top. With a little bit of digging into the source code of SpaceVim I tried the following:

call SpaceVim#layers#shell#set_variable(['terminal', 'bottom', 30, 1])

The above function is located at .SpaceVim/autoload/SpaceVim/layers/shell.vim at the line 138

That only resulted on opening the shell at the right side instead of the bottom.

Any ideas on how to change the my shell to open the way I intend it to and how can I set layer options on init.vim ?

SpaceVim's API for plugin developers' use.

Reference: https://github.com/SpaceVim/SpaceVim/issues/463

Disable conceal in latex

You may see some rendering issues in your latex files or you just want to use the original plain "text", add the code below into your init.vim

" See: http://vimdoc.sourceforge.net/htmldoc/syntax.html#g:tex_conceal
" Disable all conceal
let g:tex_conceal = ""

" Only disable math and superscripts/subscripts
let g:tex_conceal = "adg"

Explanation:

a = accents/ligatures
d = delimiters
m = math symbols
g = Greek
s = superscripts/subscripts

Reference

• http://vimdoc.sourceforge.net/htmldoc/syntax.html#g:tex_conceal
• https://stackoverflow.com/questions/18160953/disable-latex-symbol-conversion-in-vim/18161073#18161073

Teach you how to make SpaceVim become a IDE for Java

SpaceVim has leader guide feature and unite and denite layer.

These are a whole bunch of stuff. So, I have to create a new issue for reminding.

REF: #4 (comment)

Disable mouse-using in SpaceVim

Introduction

Some just doesn't like mouse-using in vim. But SpaceVim enables it by default.

You can see details in :h mouse

How to disable it?

set mouse=

BTW, you can enable it by set mouse=a or by deleting your config about mouse since SpaceVim has default value.

tar SpaceVim-v0.3.0-plugins-Linux_x86_64-offline.tar.gz failure. any solutions?

This practice only represents my personal opinion when using SpaceVim.

Mechanism: Latex Support + SpaceVim + CoC + Layer Latex(inside SpaceVim, mainly vimtex) + coc-texlab + Texlab + PDF viewer

Overview

• Installation
• SpaceVim Settings
• CoC Settings
• Preview
• Conceal
• More settings for latex layer

Installation

• LaTeX support
• Texlab binary
• SpaceVim

SpaceVim Settings

In order to enable latex support, we should complete these steps:

• let SpaceVim install coc for you
• let coc install coc-texlab
• enable latex layer

Add these configs into your ~/SpaceVim.d/init.vim to make the aforementioned steps to complete:

" Use coc to auto complete
let g:spacevim_autocomplete_method = 'coc'

" Enable layer: latex
call SpaceVim#layers#load('lang#latex')

" CoC Settings
" {{ coc {{
let g:coc_config_home = '~/.SpaceVim.d/'
let g:coc_global_extensions = [
      \ 'coc-dictionary',
      \ 'coc-word',
      \ 'coc-texlab',
      \ ]
" }} coc }}

If you need full init.vim, check dotfiles for more information.

CoC Settings

• enable latex support
• adjust texlab binary path
• enable texlab to build for us automatically

Add these config into your ~/SpaceVim.d/coc-settings.json

{
  "languageserver": {
    "latex": {
      "command": "/usr/local/bin/texlab",  // put your texlab binary path here
      "filetypes": ["tex", "bib", "plaintex", "context"]
    }
  },
  "texlab.build.onSave": true,
}

Preview

For different PDF viewer, check texlab's previewing documentation for more information.

Personally, I use Skim to forward search on MacOS.
So my settings are updated like this:

{
  "languageserver": {
    "latex": {
      "command": "/usr/local/bin/texlab",
      "filetypes": ["tex", "bib", "plaintex", "context"]
    }
  },
  "coc.source.file.ignoreHidden": false,
  "texlab.build.onSave": true,
  "texlab.build.forwardSearchAfter": true,
  "texlab.forwardSearch.executable": "/Applications/Skim.app/Contents/SharedSupport/displayline",
  "texlab.forwardSearch.args": ["-g", "%l", "%p", "%f"]  //"-g" means I want Skim to stay in the background after executing the forward search
}

Conceal

I really don't like the concealing feature, which makes it hard to write latex.
So, I disable it completely. FYI, check issue-44 for more details.

TL;DR:

let g:vimtex_syntax_conceal_default = 0

More settings for latex layer

Explanation: Latex layer is mainly about vimtex.

• Disable automatically view since I use texlab with Skim
• use <leader>v to format paragraph for me

" {{ vimtex {{
" Special setting for latex files
" Use `gggqG` to format long lines in Latex
" Use `gq11j` to wrap the line you're on with the 11 below it
" Use `gqip` or `gqap` to wrap the paragraph
" gg(go to first line), gq(format) to G(the last line)
autocmd FileType tex setlocal colorcolumn=80 textwidth=79 tabstop=2 shiftwidth=2 expandtab
nnoremap <leader>v gqip
" See: http://vimdoc.sourceforge.net/htmldoc/syntax.html#g:tex_conceal
" let g:tex_conceal = "abdg"

" Disable all syntax conceal
let g:vimtex_syntax_conceal_default = 0
" Disable automatic view since I use texlab with skim to preview in background
" personally
let g:vimtex_view_enabled = 0
let g:vimtex_view_automatic = 0
" }} vimtex }}

File: docs/quick-start-guide.md
Line: 52

- [SpaceVim Documentation](documentation/). Also known as "The Book", The SpaceVim Documentation will introduce

I think we must decide which keys to bind for language specified features, such like

• Fix imports.
• Show documentation.
• Show variables usage (in file/in project).
• Go to previous/next method
• Go to implementation.
• Go to type declaration.
• Go to super class (or method).
• Go to test class (or method).
• Rename variable.
• Fix linter errors.
• Place breakpoint.
• Start debugging.
• Override interface methods.
• Generate constructor/getter/setter/getter and setter/equals/test method

Once these key mappings are defined, contributors will be able to implement them easily.

The document could become a huge. One Single FAQ will take a lot of pages.

I think it will better if I can separate them.

Add a new SVG with SpaceVim version for documentation.

Teach you how to make SpaceVim become a IDE for JavaScript

由于本人刚使用Neovim，在 Neovim 安装SpaceVim遇到了一些问题，希望大神 解决。
1 对于新手 需要一篇详细的 Neovim安装SpaceVim的教程
2 我安装成功之后 无法使用自动补全。后来发现 是Neovim 不支持lua 也不支持python 不知道怎么解决

Add documents for Chinese users whose English isn't very good

Start to install - step 3

python -v

where -v means verbose, but -V means version. Here is part of python --help:

-v     : verbose (trace import statements); also PYTHONVERBOSE=x
-V     : print the Python version number and exit (also --version)

Teach you how to make SpaceVim become a IDE for C/C++

We all know installing SpaceVim is very easy.

But some people just don't understand how to install it and what those commands means.

So, how to install Linux is a necessary for those who know nothing about Linux.

Some people maybe have no connection to the Internet.(Yeah, a lot of people)

So, they need a post to teach them how to install SpaceVim FASTER , SAFELY and OFFLINE, including on Windows and Linux.

gvim+win7+python3+lua
按照 hackspacevim 的教程安装的，改做的都做了，初次进入gvim，安装插件时，其他插件都是 installing done，但是 vimproc.vim 就显示 *vimproc.vim Building，一直都没有done。build vimproc.vim 还有其他环境要求，还是什么问题

Preface

Now, SpaceVim only has vim2048 embedded.

You have to wait if you want to play more.

Instructions

1. Add config into your ~/.SpaceVim.d/init.vim below:

call SpaceVim#layers#load('games')

2. Open your vim/neovim
   You should see this:
   

3. Restart vim, and Press <Space> g 2:

4. DONE!
   

I forget to add installing ctags on Linux and Windows.

Exuberant ctags not found

For a long time ago, I've been looking forward to the discussions in GitHub. I believe that any documents about vim or SpaceVim is not enough for users to get what they want to know.

The best way for vim users is to use a "system" like StackOverflow. However, StackOverflow is too serious for this small document-like project. Therefore, Discussions can play an important role in this project.

Therefore, I recommend other users could also try to use Discussions in GitHub.

I really want this project could help others learn how to use vim or SpaceVim efficiently and correctly, also, quickly as possible.

PS: I hope this project could accumulate the knowledge provided in Discussions from time to time if Discussions is welcome by others as well.

I want this to have a very good, at least good, directory structure for the search or reference for users.

So, anybody could find what he wants without wasting too much time.

Many distros of Linux may not have the latest version of vim.

Some people just don't know how to build vim from source.

This issue is for future use.
location:

• ~/.SpaceVim.d/init.toml
• ~/.SpaceVim.d/init.vim(recommended for advanced users)
  NOTE: DO NOT make any changes in ~/.SpaceVim/init.toml or ~/.SpaceVim.d/init.vim.

init.toml could make the source code of SpaceVim dirty so that I personally do not recommend to use it. USE IT AT YOUR OWN RISK!

init.toml

See in: #10 (comment)

init.vim

See in: #10 (comment)

PS: You may want to check my own config file for your convenience: https://github.com/Gabirel/dotfiles/blob/master/.SpaceVim.d/init.vim

• Pictures will be hosting on Gist-Hack-SpaceVim instead of Hack-SpaceVim
• Fixed spell: SpaceVim
• DO NOT ADD / before folder when using relative path in TOC.
  • correct: installation/installation-for-windows.md ✅
  • wrong: /installation/installation-for-windows.md ❌
• Markdown Lint Rule: Rules.md
• The first word of English title should be capitalized.
• Use Asciidoc to avoid wasting time to update TOC.
• Hack-SpaceVim is where the knowledge aggregation belongs, originating from GitHub issue and GitHub discussion.

That would be super awesome to get process of setting up SpaceVim for Elixir development documented.

Many people may confused about how to install SpaceVim on Windows.

So, I decide to write an instructions about how to install SpaceVIm on your Windows and make sure I can solve all the problems when installing.

Everyone may lose his directions without basic instructions for SpaceVim has a very good UI, which is pretty good, and massive commands embedded. Everybody may get confused when using SpaceVim firstly. Or, you may forgot how to what kind of shortcuts to meet your work.

So, commonly used shortcuts have to get put out to let users know what kind of shortcuts they have to know.

What is true color?

Why SpaceVim choose to use true colors by default?

Come from: #4 (comment)

I just check the readme, the links before the toc makes me confused. the alt text is 中文文档 and English Document, but this link is not http://spacevim.org/documentation/ and http://spacevim.org/cn/documentation/

the resource of SpaceVim is:

1. SpaceVim's github is for developers
2. SpaceVim's website and documentation is for users
3. Hack-SpaceVim's issue is for ask question about how to hack SpaceVim
4. SpaceVim's issue is for bug report and feature requst

so how about:

SpaceVim | Hack-SpaceVim 中文版 | Ask question | Bug report & Feature request

I think we must decide which keys to bind for language specified features, such like

• Fix imports.
• Show documentation.
• Show variables usage (in file/in project).
• Go to previous/next method
• Go to implementation.
• Go to type declaration.
• Go to super class (or method).
• Go to test class (or method).
• Rename variable.
• Fix linter errors.
• Place breakpoint.
• Start debugging.
• Override interface methods.
• Generate constructor/getter/setter/getter and setter/equals/test method

Once these key mappings are defined, contributors will be able to implement them easily.

SpaceVim Health checking :

SpaceVim clipboard support check report:
Checking +clipboard:
SUCCEED!
SpaceVim environment check report:
Current progpath: gvim.exe(C:\Program Files\vim80\gvim.exe)
version: 800
OS: Windows
[shell, shellcmdflag, shellslash]: ['C:\Windows\system32\cmd.exe', '/c', 0]
SpaceVim lua support check report:
Checking +lua:
SUCCEED!
SpaceVim python support check report:
Checking +python3:
SUCCEED!
Checking +python:
SUCCEED!

TL;DR

use :verbose set conceallevel? concealcursor? to find out what plugins make your conceal weird.

Source

You can see this: https://github.com/SpaceVim/SpaceVim/issues/2033#issuecomment-417756611

This is because your version of vim is lower than vim(v7.4.1325).
You have to upgrade your vim to higher version with +job feature.

vim with +job(Higher Version):

vim with -job(Lower Version):

Thanks @unixcx

In 'en_US/IDE/JavaScript.md' the bash command used to install tern server is pretty confusing as GitHub outputs the MarkDown using the quotation shortcodes:

> cd ~/.cache/vimfiles/repos/github.com/ternjs/tern_for_vim 
> npm install tern

in a single line, I have written a PR to make use of the GitHub version of MarkDown to make it more clear for everyone.