neovim终于把out of box放到roadmap里了

Mantis-Shrimp · 2025 年1 月 27 日 14:42

neovim太多常用的功能没有内置了，lsp-config treesitter which-key 等等

ashfinal · 2025 年1 月 27 日 16:12

github.com/neovim/neovim

feat(lsp): add `vim.lsp.config` and `vim.lsp.enable`

neovim:master ← lewis6991:feat/lspsetup

opened 04:45PM - 01 Nov 24 UTC

lewis6991

+601 -76

## Problem - Setting up LSP clients require unnecessary boilerplate. - LSP c…onfiguration has no system. ## Solution Add `vim.lsp.enable()` and `vim.lsp.config()`. ### Design goals/requirements: - Default configuration of a server can be distributed across multiple sources. - And via RTP discovery. - Default configuration can be specified for all servers. - Can extend capabilities of all clients. - Configuration _can_ be project specific. ### Proposal: - Two new API's: - `vim.lsp.config(name, cfg)`: - Used to define configurations for servers of name. - Can be used like a table or called as a function. - Use `vim.lsp.config(name, cfg)` to extend a configuration - Use `vim.lsp.config[name] = cfg` to define a configuration - Use `vim.lsp.confg('*', cfg)` to specify default config for all servers. - Examples: ```lua -- Set default root marker for all clients vim.lsp.config('*', { root_markers = { '.git' }, }) -- Set default configuration for clangd but don't enable it vim.lsp.config.clangd = { cmd = { 'clangd', '--clang-tidy', '--background-index', '--offset-encoding=utf-8', }, root_markers = { '.clangd', 'compile_commands.json' }, filetypes = { 'c', 'cpp' }, } ``` - `vim.lsp.enable(name)` - Used to enable servers of name. Uses configuration defined via `vim.lsp.config()`. - Examples: ```lua vim.lsp.enable('clangd') ``` - Client configuration sources `lsp/<name>.lua` to resolve configurations. - Only done once per enabled configuration. - Redone if `vim.lsp.config[name]` is accessed (read or modified). ### Notes: - Instead of adding `vim.lsp.config(name, cfg)` I considered `vim.lsp.enable(name, cfg, config_only)` where `vim.lsp.enable(name, cfg, true) === vim.lsp.config(name, cfg)`. I decided against this since I felt a `config_only` field is slightly more confusing, harder to explain and less generally appealing than having `vim.lsp.config`. There is also some parallel to `vim.diagnostic.enable` and `vim.diagnostic.config`. If there is pushback to this, then I can remove that from this PR, and add it to a separate future PR for further consideration. - This PR doesn't provide a full solution for project specific config, but I'm pretty sure doesn't inhibit it. Though I think for most cases using things like `workspace/didChangeConfiguration` in `on_attach` or `LspAttach` should be sufficient. - This PR is not intended to be the final end goal of LSP configuration but just a medium term stepping stone that moves us forward in the right direction. Going forward I'd expect us to add some options into the native option system to complement (or replace) what is added here: - Buffer local options: - `:setlocal lsp+=clangd` - `:setlocal root_marker+=compile_commands.json` - LSP namespaced specific options: - `:set lsp_servers.clangd.cmd=['clangd']` - Continuation of #18506 ### Todo: - [x] News - [x] Documentation - [x] Tests - [x] Health check ### Future considerations - Consider allowing a table to be returned from `lsp/*.lua`. - Better accommodate project specific configurations.

lsp-config 已经合并，我还没有看。根据说法，没有深度客制化需求的话，只需要类似 vim.lsp.enable('clangd') 就可以启用了。

treesitter 没有更激进的分发，是因为很多语言支持不够成熟，需要用户保持最新版本、参与测试、以及需要时间处理类似 html 嵌入 javascirpt、css 等多语的问题。

个人一直不喜欢 which-key

Mantis-Shrimp · 2025 年1 月 27 日 16:15

你不用which key？

ashfinal · 2025 年1 月 27 日 16:23

全局性的菜单有点累赘，至少应该根据当前 context 弹出。偶尔忘了绑定，搜下就好。vim.keymap.set 有 desc 描述字段，基本所有插件早就普及了吧。搜描述就好。