Request for sample config (lazy + vim.lsp.config w/ clangd + rust-analyzer)

[bwidawsk]

I've been trying to use blink since the earliest days. I've never quite had the setup I'd like with nvim-lspconfig. I'm really excited to try vim.lsp.config but haven't managed to figure out the best practice for using this with blink.

Thanks

[bwidawsk]

To add some more context. I seem to just not get the completion trigger and so I never see the trigger menu. This was working mostly with nvim-lspconfig beforehand.

[krovuxdev]

@bwidawsk I’m not sure if you’ve tried this?

local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities = vim.tbl_deep_extend("force", capabilities, require("blink.cmp").get_lsp_capabilities())
--- `*` for global servers
vim.lsp.config("*", {
    --- it’s not necessary to add capabilities
    --- because blink.cmp is already configured as per https://github.com/Saghen/blink.cmp/blob/main/plugin/blink-cmp.lua
    capabilities = capabilities,
})
local
vim.lsp.config("lua_ls", {
        cmd = { "lua-language-server" }, -- it is important to have a cmd to execute the LSP for lua_ls
        filetypes = { "lua" },
})
vim.lsp.enable("lua_ls")

It works fine for me with this setup.

[bwidawsk]

Thanks @krovuxdev for the advice - actually lua seemed to work properly it was just my clangd setup. I believe I finally figured out the problem where I was using native completions in a lost config file. I don't yet have Rust integrated, but I'm not doing Rust development at the moment.

Here is a snapshot of my now working config. The only thing that maybe makes it slightly unique is I do android native development and so I have diverging clangd for that vs. normal c++ projects.

bc012769ae31c4a70a3b83b6d28d3257688850fd