Justin M. Keyes

This kind of stuff is common because of all the asynchronous logic happeing. We need to start building up some util functions that do something reasonable if buffer contents change...

I think we'll need this concept for all kinds of namespaces. Discussed in https://github.com/neovim/neovim/issues/32261

Related: - https://github.com/neovim/neovim/pull/33771 > Have a readonly `root_dir` or `project_root` buffer variable Does https://github.com/neovim/neovim/pull/33320 address that, or should we drop the `:bcd` idea?

Having both seems a bit much. It sounds to me like `:bcd` may be the wrong direction.

> From what I understand `bcd` was wanted for different reasons. Basically the same as `tcd` but for buffers. No, the discussion in https://github.com/neovim/neovim/issues/33318 seems clearly motivated by "root directory"...

> Have `root_markers` definitions as part of filetype plugins or buffer variable Based on observation of nvim-lspconfig, a filetype's root_markers may change based on the LSP client(s) attached. E.g. a...

> Restoring these lines removed in [#36503](https://github.com/neovim/neovim/pull/36503) fixes the issue, but it triggers an unnecessary re-parse Doesn't seem like a good tradeoff. Maybe it could check window height to avoid...

Try `vim.lsp.config` in Nvim 0.11 (unreleased) https://github.com/neovim/neovim/pull/31031

Sorry I missed that :D That is good news. We can keep this open, but will probably close all of these nvim-lspconfig "framework" issues once Nvim 0.11 is released. nvim-lspconfig...

No longer relevant since we migrated to `vim.lsp.config`