lvimuser

Debugging codelens works with ```lua -- https://github.com/simrat39/rust-tools.nvim#a-better-debugging-experience local path = vim.fn.glob(vim.fn.stdpath("data") .. "/mason/packages/codelldb/extension/") or "" local codelldb_path = path .. "adapter/codelldb" local liblldb_path = path .. "lldb/lib/liblldb.so" if vim.fn.filereadable(codelldb_path) and...

Related: https://github.com/hrsh7th/nvim-cmp/pull/1148 fwiw, the behavior is consistent with vscode (editor.suggest.insertMode set to replace) for both clangd and pylance Possible patch ```diff diff --git a/lua/cmp/entry.lua b/lua/cmp/entry.lua index 6fa5460..7d9e023 100644 --- a/lua/cmp/entry.lua...

> I tried editor.suggest.insertMode = replace and there is one difference. When the word exactly matches the suggestion, vscode does not change it. So behavior is not consistent after all....

Seems fine to me on rolling, it opens on the same line `import ()` then, after `` inside the parenthesis, I get ``` import ( | ) ```

Possibly related https://github.com/LunarVim/LunarVim/issues/2935 There's not enough information, what's the output of `:LspLog`?

Output of `:NullLsLog` ? Most common cause is the formatters/linters are not available in your path. If the client is attached, `null-ls` has started, so the issue's title is misleading.

Unlikely, why should this be a default? You can add it as a plugin. Might want to look into https://github.com/ap29600/tree-sitter-odin

What's the output of `:LspLog` ? cc @dgabka

Try `args = { "--filter", "-legal/copyright" }`. Might be worth checking the logs to make sure the args are being passed. (`:NullLsLog`, but need to set the debug flag).

>How do I set debug flag? `lvim.lsp.null_ls.setup["debug"] = true`