Closed eshepelyuk closed 3 months ago
cc @He1pa
Thanks for your suggestion, I'll test it
Thanks for your suggestion, I'll test it
This is minimal config using vim-plug
, test.init.vim
call plug#begin(stdpath('data') . '/plugged')
Plug 'eshepelyuk/kcl.nvim'
Plug 'neovim/nvim-lspconfig'
call plug#end()
lua << EOF
local server_config = require("lspconfig.configs")
local util = require("lspconfig.util")
server_config.kcl = {
default_config = {},
}
require("lspconfig").kcl.setup({
cmd = { "kcl-language-server" },
filetypes = { "kcl" },
root_dir = util.root_pattern(".git"),
})
EOF
nvim -u test.init.vim some.k
Here's a screenshot running : LspInfo
from nvin-lspconfig
Thanks a lot, I tested it and it works for both lazy.vim and vim-plug. I have submitted a PR to modify them
@He1pa all works fine, thankx a lot.
Hello,
Currently plugin relies on combination of plugin manager setting (like lazyvim) and internal code to manage start of LSP servers. This causes few bugs (like in #10 ) and removes portability between different plugin managers.
I've been playing with my fork and
nvim-lspconfig
and I realize that lsp related code can be completely removed and offloaded tonvim-lspconfig
.Having
nvim-lspconfig
plugin added via your plugin manager and configuringnvim-lspconfig
like thisIt's possible to remove
lsp/init.lua
andlsp/handlers.lua
and everything will keep working. More over, those files are overriding user's LSP settings, like diagnostics, that is undesirable.So basically, this plugin may only provide syntax highligh and comment string - and with
nvim-lspconfig
it will be enough.