Justin M. Keyes

# Resolution Commands defined by LSP configs are required to start with `:Lsp*`. That, plus other guidance, is enforced by CI lint check: https://github.com/neovim/nvim-lspconfig/issues/1937#issuecomment-2819257770 . That addresses the main story...

> Isn't a vim.system call to git ls-files + post processing via vim.glob good enough? Could be. Then we just need to document it :)

> What about `vim.vcs.git.files()` or something of the sort? That's a different topic, which has a 10x bigger scope than this incremental step.

- https://github.com/neovim/nvim-lspconfig/pull/3666 not needed because `vim.system()` can be used instead

@TheRealLorenz FWIW, may be helpful: https://github.com/neovim/neovim/issues/32037#issuecomment-2825599872 : `root_dir()` can be used to conditionally (per-file) decide whether to enable lsp.

Send a pr. "single-file support" is the *default* in `vim.lsp.config`, and Nvim 0.11.1 added `workspace_required` flag to allow configs to *disable* "single-file support".

@FedeAbella my [current suggestion](https://github.com/neovim/nvim-lspconfig/pull/3900#issuecomment-2962998290) is to define `reuse_client` and define `cmd()` as function. There is sample code given there. Please open a new PR or issue for further discussion, to...

https://github.com/neovim/nvim-lspconfig/pull/4081 shows an interesting way to get the `on_new_config` effect with `vim.lsp.config`.

@GaetanLepage as you can see from the above list, https://github.com/neovim/nvim-lspconfig/blob/master/lsp/bitbake_language_server.lua needs `workspace_required=true` (the equivalent to the old `single_file_support = false`). > Also, are `bitbake_language_server` and `bitbake_ls` the same thing? Look...

> For `vim.diagnostic.setqflist()` the current trend is `q` idk where that "trend" came from, but it's a really bad choice. `grq` seems like an ok choice. > `grl` is a...