Here are mappings for vim-lsp in the lsp layer.
Makes use of #496.
Regarding the if get(b:, 'spacevim_lsp_engine', g:spacevim_lsp_engine) ==# 'vim_lsp': I'm thinking it could be possible to have the lsp engine depend on the buffer... maybe there is a good use-case for that. ~I've not tested that yet.~ Might be useful? I should probably simplify that to g:spacevim_lsp_engine ==# 'vim_lsp' for now.
EDIT:b:spacevim_lsp_engine seems to work well in terms of keymappings. Though the lsp layer would need to be revised to load each engine, if say g:spacevim_lsp_engine is a list of engines. Much of core/autoload/spacevim/lang/util.vim would be moved into the lsp layer's config.vim. I think some people might be interested in using b:spacevim_lsp_engineper language. Anyway, probably best to put that feature in a different PR.
Here are mappings for vim-lsp in the lsp layer. Makes use of #496.
Regarding the
if get(b:, 'spacevim_lsp_engine', g:spacevim_lsp_engine) ==# 'vim_lsp': I'm thinking it could be possible to have the lsp engine depend on the buffer... maybe there is a good use-case for that. ~I've not tested that yet.~ Might be useful? I should probably simplify that tog:spacevim_lsp_engine ==# 'vim_lsp'for now. EDIT:b:spacevim_lsp_engineseems to work well in terms of keymappings. Though the lsp layer would need to be revised to load each engine, if sayg:spacevim_lsp_engineis a list of engines. Much ofcore/autoload/spacevim/lang/util.vimwould be moved into the lsp layer'sconfig.vim. I think some people might be interested in usingb:spacevim_lsp_engineper language. Anyway, probably best to put that feature in a different PR.Contingent on: #496