nvim-lspconfig/lsp/robotcode.lua, branch docs

feat(robotcode): support virtual env #4367

2026-04-03T15:01:32Z

fix: separate type annotation from `@brief` docstring #4017

2025-08-20T02:13:01Z

chore: add type annotation for configs

2025-08-19T02:39:23Z

docs: cleanup

2025-04-18T15:44:38Z

- brief should live at the top of each file - fix indentation for some docs

fix(docs): docgen.lua reads from `lua/*.lua` #3708

2025-04-13T02:40:01Z

Problem: Since configs now live in `lsp/`, the docgen needs to be updated. Solution: Read the configs from `lsp/`. Parse the `@brief` docstring to get the docs.

feat: migrate to vim.lsp.config #3659

2025-04-12T22:15:43Z

Problem: Nvim 0.11 has vim.lsp.config, which mostly replaces the legacy nvim-lspconfig "framework". Solution: Migrate all configs to `lsp/*` variants. The old configs in `lua/lspconfig/` are "frozen". The new configs include these changes: - `commands` field became raw calls to `vim.api.nvim_buf_create_user_command` inside `on_attach`. - `root_dir` became: - `root_markers` whenever the file list was simple didn't need to mach `*` - if the logic was complicated, or needed to match something like '\*.c', it was defined as a vim.lsp.Config `root_dir` callback. - `on_config_change` became `before_init`. I don't actually know if this is the correct approach, but looking around the documentation of `nvim-lspconfig` a saw that it was defined as the function that gets called as soon as the config have `root_dir`, and so I thought `before_init` might be the closest alternative. - `docs.description` became a luadoc `@brief` docstring. - `single_file_support = false`? Co-authored-by: Aliou Diallo Co-authored-by: Justin M. Keyes