Hmmm this shouldn't be necessary if you're using nvim-lspconfig, which specifies cmd for you.

Yes, but the docs only mention to use nvim-lspconfig with neovim 0.10. For 0.11+, the native vim.lsp.config is mentioned, which does not contain a ty configuration natively.

Instead of adding a lspconfig recommendation also for 0.11+, I think it would be helpful to show the required lsp command for those who don't want to use neovim's native lsp capabilities without installing a separate plugin.

I'm not sure we should be optimizing the docs for the case where nvim-lspconfig isn't being used. I'd rather the docs target nvim-lspconfig to keep things simpler (particularly if and when the ty config innvim-lspconfig gets more complicated). For users looking to keep things lean and not use any plugins, I think they can go to nvim-lspconfig and copy the configuration from there.

I say this because some of the configs can be rather complicated. I don't know if ty's will ever get to that level, but if it does, I'd rather just point folks toward nvim-lspconfig instead of reproducing a complex config in our docs.

I'm not sure we should be optimizing the docs for the case where nvim-lspconfig isn't being used. I'd rather the docs target nvim-lspconfig to keep things simpler (particularly if and when the ty config innvim-lspconfig gets more complicated). For users looking to keep things lean and not use any plugins, I think they can go to nvim-lspconfig and copy the configuration from there.

I say this because some of the configs can be rather complicated. I don't know if ty's will ever get to that level, but if it does, I'd rather just point folks toward nvim-lspconfig instead of reproducing a complex config in our docs.

That seems reasonable, I'll close this out.

That makes sense! Maybe it's still possible to clarify the text a bit to highlight that nvim-lspconfig is recommended also for Neovim >=0.11? I made a suggestion in #2785 as a continuation of this PR