retronvim 0.4.8__py3-none-any.whl

data/nvim/plugins/nvim-lspconfig/CONTRIBUTING.md

@@ -0,0 +1,203 @@
+# Contributing to nvim-lspconfig
+
+## Requirements
+
+- [Lint requirements](#lint)
+- Documentation is generated by `scripts/docgen.lua`.
+  - Only works on linux and macOS
+
+## Scope of nvim-lspconfig
+
+The purpose of nvim-lspconfig is to provide configuration so that users can activate LSP with a single `vim.lsp.enable('foo')` call.
+It must not provide its own "framework". Any "framework" or "util" code must be upstreamed to Nvim core.
+
+## Pull requests (PRs)
+
+- Mark your pull request as "draft" until it's ready for review.
+- Avoid cosmetic changes to unrelated files in the same commit.
+- Use a **rebase workflow** for small PRs.
+  - After addressing review comments, it's fine to rebase and force-push.
+
+## New config
+
+### Criteria
+
+New configs must meet these criteria (to avoid spam/quasi-marketing/vanity projects):
+
+- GitHub Stars: The server repository should have at least 100 stars, or some other evidence (such as vscode marketplace downloads) that the LSP server is reasonably popular and is not spam/quasi-marketing/vanity projects.
+- Provide some reference or evidence that the language targeted by the LSP server has an active user base.
+
+This helps ensure that we only include actively maintained and widely used servers to provide a better experience for
+the community.
+
+### Walkthrough
+
+To add a new config, copy an existing config from `lsp/`. Start with `lsp/lua_ls.lua` for a simple a config, or `lsp/jdtls.lua` or `lsp/pyright.lua` for more complex examples.
+
+When choosing a config name, convert dashes (`-`) to underscores (`_`). If the name of the server is a unique name (`pyright`, `clangd`) or a commonly used abbreviation (`zls`), prefer this as the server name. If the server instead follows the pattern x-language-server, prefer the convention `x_ls` (`jsonnet_ls`). 
+
+The minimal config properties are:
+
+* `cmd`: command defined as a string list, where the first item is an executable and following items are its arguments (`--stdio` is common).
+  ```lua
+  cmd = { 'typescript-language-server', '--stdio' }
+  ```
+* `filetypes`: list of filetypes that should activate this config.
+* `root_markers`: a list of files that mark the root of the project/workspace.
+    * See `:help lsp-config`.
+    * See `vim.fs.root()`
+
+### Commands
+
+LSP servers may provide custom `workspace/executeCommand` commands. Because LSP does not provide any way for clients to programmatically discover/list these commands, configs may define user commands in Nvim which invoke the `workspace/executeCommand` commands. To keep things maintainable and discoverable, configs must follow these guidelines:
+
+- The server-specific user commands must be buffer-local and must be created in the `on_attach` handler.
+  - Be sure to use the `bufnr` passed as the 2nd argument to `on_attach` to refer to the buffer that the server has been attached to, as it may be different from the current buffer!
+- The names of these commands must be prefixed with `:Lsp`. This is a crude way to improve "discoverability".
+- Do NOT create commands that merely alias existing *code-actions* or *code-lenses*, which are *already* auto-discoverable via the ["gra" keymap](https://neovim.io/doc/user/lsp.html#gra) (or `vim.lsp.buf.code_action()`)
+- Use `client:exec_cmd()` (instead of `request(..., 'workspace/executeCommand')`)
+
+### Schemas
+
+If possible, add the JSON schema for the LS to the index in [gen_json_schemas.lua](https://github.com/neovim/nvim-lspconfig/blob/3addf05a791ea256c36438220aced91c03071712/scripts/gen_json_schemas.lua#L2). CI will autogenerate LuaLS types from the schema. See [Generated LSP "settings" types](#generated-lsp-settings-types).
+
+### Example
+
+Following is an example new config for `lsp/pyright.lua`:
+
+```lua
+---@brief
+---
+--- https://github.com/microsoft/pyright
+---
+--- `pyright`, a static type checker and language server for python
+return {
+  cmd = { 'pyright-langserver', '--stdio' },
+  filetypes = { 'python' },
+  root_markers = {
+    'pyproject.toml',
+    'setup.py',
+    'setup.cfg',
+    'requirements.txt',
+    'Pipfile',
+    'pyrightconfig.json',
+  },
+  ---@type lspconfig.settings.pyright
+  settings = {
+    python = {
+      analysis = {
+        autoSearchPaths = true,
+        useLibraryCodeForTypes = true,
+        diagnosticMode = 'workspace',
+      },
+    },
+  },
+  on_attach = function(client, bufnr)
+    vim.api.nvim_buf_create_user_command(bufnr, 'LspPyrightOrganizeImports', function()
+      client:exec_cmd({
+        command = 'pyright.organizeimports',
+        arguments = { vim.uri_from_bufnr(bufnr) },
+      })
+    end, {
+      desc = 'Organize Imports',
+    })
+  end,
+}
+```
+
+### Root marker priority
+
+By default, the [`root_markers` field](https://neovim.io/doc/user/lsp.html#lsp-root_markers) is ordered by priority.
+However, configs can specify "equal priority" (since Nvim 0.11.3) by placing names in a nested list.
+
+For example in this config, `'package.json'` and `'tsconfig.json'` have *equal* priority, whereas `'.git'` has lower priority.
+
+```lua
+return {
+  …
+  root_markers = { { 'package.json', 'tsconfig.json' }, { '.git' } }
+}
+```
+
+Since nvim-lspconfig still supports Nvim older than 0.11.3, avoid the "nested list" form on older versions of Nvim:
+
+```lua
+return {
+  …
+  root_markers = vim.fn.has('nvim-0.11.3') == 1
+    and { { 'package.json', 'tsconfig.json' }, { '.git' } }
+    or { 'package.json', 'tsconfig.json', '.git' }
+}
+```
+
+## Rename or deprecate a config
+
+If a config needs to be renamed or deprecated, changes its contents like this:
+
+```lua
+---@brief
+---
+--- Renamed to [systemd_lsp](#systemd_lsp)
+
+---@type vim.lsp.Config
+return vim.tbl_extend('force', vim.lsp.config.systemd_lsp, {
+  on_init = function(...)
+    vim.deprecate('systemd_ls', 'systemd_lsp', '3.0.0', 'nvim-lspconfig', false)
+    if vim.lsp.config.systemd_lsp.on_init then
+      vim.lsp.config.systemd_lsp.on_init(...)
+    end
+  end,
+})
+```
+
+## Commit style
+
+Follow the Neovim core [commit message guidelines](https://github.com/neovim/neovim/blob/master/CONTRIBUTING.md#commit-messages). Examples:
+
+* Adding a new config for "lua_ls":
+  ```
+  feat: lua_ls
+  ```
+* Fixing a bug for "lua_ls":
+  ```
+  fix(lua_ls): update root directory pattern
+
+  Problem:
+  Root directory incorrectly prefers "foo".
+
+  Solution:
+  Rearrange the root dir definition.
+  ```
+
+## Lint
+
+PRs are checked with the following analyzers:
+- [luals](https://github.com/LuaLS/lua-language-server)
+- [stylua](https://github.com/JohnnyMorganz/StyLua).
+
+To run the linter locally:
+
+    make lint
+
+If using nix, you can use `nix develop` to install these to a local nix shell.
+
+## Generating docs
+
+GitHub Actions automatically generates `configs.md`. Only modify
+`scripts/docs_template.md` or the docstrings in the source of the config file.
+Do not modify `configs.md` directly.
+
+To preview the generated `configs.md` locally, run `scripts/docgen.lua` from
+`nvim` (from the project root):
+
+    HOME=./ nvim --clean -R -Es -V1 +'set rtp+=$PWD' +'luafile scripts/docgen.lua'
+
+## Generated LSP "settings" types
+
+The `@class` declarations in `lua/lspconfig/types/lsp/*.lua` are generated by
+`scripts/gen_annotations.lua`. The JSON schema index is manually maintained
+in [gen_json_schemas.lua](https://github.com/neovim/nvim-lspconfig/blob/3addf05a791ea256c36438220aced91c03071712/scripts/gen_json_schemas.lua#L2).
+
+The `package.json` follows the standard Node.js format, and VS Code uses
+a [custom `contributes.configuration` field](https://github.com/neovim/nvim-lspconfig/blob/3addf05a791ea256c36438220aced91c03071712/scripts/gen_json_schemas.lua#L191)
+to define the JSON Schema for `settings.json`.

data/nvim/plugins/nvim-lspconfig/LICENSE.md

@@ -0,0 +1,176 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

data/nvim/plugins/nvim-lspconfig/Makefile

@@ -0,0 +1,10 @@
+test:
+	vusted ./test
+
+lint:
+	@printf "\nRunning stylua\n"
+	stylua --check .
+	@printf "\nRunning emmylua\n"
+	emmylua_check .
+
+.PHONY: test lint

data/nvim/plugins/nvim-lspconfig/README.md

@@ -0,0 +1,229 @@
+# nvim-lspconfig
+
+nvim-lspconfig is a collection of LSP server configurations for the [Nvim LSP client](https://neovim.io/doc/user/lsp.html).
+
+View [all configs](doc/configs.md), or run `:help lspconfig-all` from Nvim.
+
+## Important ⚠️
+
+* `require('lspconfig')` (the legacy "framework" of nvim-lspconfig) [is **deprecated**](https://github.com/neovim/nvim-lspconfig/issues/3693) in favor of [vim.lsp.config](https://neovim.io/doc/user/lsp.html#lsp-config) (Nvim 0.11+).
+    * The [lspconfig.lua](./lua/lspconfig.lua) *module* will be dropped. Calls to `require('lspconfig')` will show a warning, which will later become an error.
+* nvim-lspconfig itself is **NOT deprecated**. It provides server-specific configs.
+    * The configs live in the [lsp/](./lsp/) directory. `vim.lsp.config` automatically finds them and merges them with any local `lsp/*.lua` configs defined by you or a plugin.
+    * The old configs in [lua/lspconfig/](./lua/lspconfig/) are **deprecated** and will be removed.
+
+### Migration instructions
+
+1. Upgrade to Nvim 0.11+
+2. (Optional) Use `vim.lsp.config('…')` (not `require'lspconfig'.….setup{}`) to *customize* or *define* a config.
+3. Use `vim.lsp.enable('…')` (not `require'lspconfig'.….setup{}`) to *enable* a config, so that it activates for its `filetypes`.
+
+## Support
+
+These configs are **best-effort and supported by the community (you).** See [contributions](#contributions).
+
+* Ask questions on [GitHub Discussions](https://github.com/neovim/neovim/discussions), not the issue tracker.
+* If you found a bug in Nvim LSP (`:help lsp`), [report it to Neovim core](https://github.com/neovim/neovim/issues/new?assignees=&labels=bug%2Clsp&template=lsp_bug_report.yml).
+    * **Do not** report it here. Only configuration data lives here.
+
+## Install
+
+[![LuaRocks](https://img.shields.io/luarocks/v/neovim/nvim-lspconfig?logo=lua&color=purple)](https://luarocks.org/modules/neovim/nvim-lspconfig)
+
+* Requires Nvim 0.11.3+.
+    * Support for Nvim 0.10 [will be removed](https://github.com/neovim/nvim-lspconfig/issues/3693). Upgrade Nvim and nvim-lspconfig before reporting an issue.
+* With Nvim 0.12+, you can use the builtin `vim.pack` plugin manager:
+  ```lua
+  vim.pack.add{
+    { src = 'https://github.com/neovim/nvim-lspconfig' },
+  }
+  ```
+* Or install nvim-lspconfig using Vim's "packages" feature:
+  ```
+  git clone https://github.com/neovim/nvim-lspconfig ~/.config/nvim/pack/nvim/start/nvim-lspconfig
+  ```
+* Or use a 3rd-party plugin manager.
+
+## Quickstart
+
+1. Install a language server, e.g. [pyright](doc/configs.md#pyright)
+   ```bash
+   npm i -g pyright
+   ```
+2. Enable its config in your init.lua ([:help lsp-quickstart](https://neovim.io/doc/user/lsp.html#lsp-quickstart)).
+   ```lua
+   vim.lsp.enable('pyright')
+   ```
+3. Ensure your project/workspace contains a root marker as specified in `:help lspconfig-all`.
+4. Open a code file in Nvim. LSP will attach and provide diagnostics.
+   ```
+   nvim main.py
+   ```
+5. Run `:checkhealth vim.lsp` to see the status or to troubleshoot.
+
+See `:help lspconfig-all` for the full list of server-specific details. For
+servers not on your `$PATH` (e.g., `jdtls`, `elixirls`), you must manually set
+the `cmd` parameter:
+
+```lua
+vim.lsp.config('jdtls', {
+  cmd = { '/path/to/jdtls' },
+})
+```
+
+## Commands
+
+* `:LspInfo` (alias to `:checkhealth vim.lsp`) shows the status of active and configured language servers.
+* `:lsp enable [<config_name>]` (`:LspStart` for Nvim 0.11 or older) Start the requested server name. Will only successfully start if the command detects a root directory matching the current config.
+* `:lsp disable [<config_name>]` (`:LspStop` for Nvim 0.11 or older) Stops the given server. Defaults to stopping all servers active on the current buffer. To force stop use `:LspStop!`
+* `:lsp restart [<client_name>]` (`:LspRestart` for Nvim 0.11 or older) Restarts the given client, and attempts to reattach to all previously attached buffers. Defaults to restarting all active servers.
+
+## Configuration
+
+Nvim sets default options and mappings when LSP is active in a buffer:
+* [:help lsp-defaults](https://neovim.io/doc/user/lsp.html#lsp-defaults)
+* [:help diagnostic-defaults](https://neovim.io/doc/user/diagnostic.html#diagnostic-defaults)
+
+To customize, see:
+* [:help lsp-attach](https://neovim.io/doc/user/lsp.html#lsp-attach)
+* [:help lsp-buf](https://neovim.io/doc/user/lsp.html#lsp-buf)
+
+Extra settings can be specified for each LSP server. With Nvim 0.11+ you can
+[extend a config](https://neovim.io/doc/user/lsp.html#lsp-config) by calling
+`vim.lsp.config('…', {…})`.
+
+```lua
+vim.lsp.config('rust_analyzer', {
+  -- Server-specific settings. See `:help lsp-quickstart`
+  settings = {
+    ['rust-analyzer'] = {},
+  },
+})
+```
+
+### Config priority
+
+Configs are sourced in this order:
+
+1. `lsp/` in 'runtimepath'
+2. `after/lsp/` in 'runtimepath'
+3. `vim.lsp.config()`
+
+If you install nvim-lspconfig or similar plugins, the order that configs are applied depends on the load order. To ensure that your own config "wins" and overrides the others, use `after/lsp/` and/or `vim.lsp.config()` to override/extend the defaults.
+
+## Creating a config
+
+### As code
+
+1. Run `:lua vim.lsp.config('foo', {cmd={'true'}})`
+2. Run `:lua vim.lsp.enable('foo')`
+3. Run `:checkhealth vim.lsp`, the new config is listed under "Enabled Configurations". 😎
+
+### As a file
+
+1. Create a file `after/lsp/foo.lua` somewhere on your 'runtimepath'.
+   ```
+   :exe 'edit' stdpath('config') .. '/after/lsp/foo.lua'
+   ```
+2. Add this code to the file (or copy any of the examples from the [lsp/ directory](./lsp/) in this repo):
+   ```
+   return {
+     cmd = { 'true' },
+   }
+   ```
+3. Save the file (with `++p` to ensure its parent directory is created).
+   ```
+   :write ++p
+   ```
+4. Enable the config.
+   ```
+   :lua vim.lsp.enable('foo')
+   ```
+5. Run `:checkhealth vim.lsp`, the new config is listed under "Enabled Configurations". 🌈
+
+## LSP Settings Type Annotations
+
+`nvim-lspconfig` generates Lua type definitions for each supported LSP server.
+By manually adding annotations (e.g., `---@type lspconfig.settings.server_name`),
+you enable auto-completion and diagnostics for your server settings.
+
+**Example:**
+
+```lua
+---@type vim.lsp.Config
+local config = {
+  ---@type lspconfig.settings.lua_ls
+  settings = {
+    Lua = {
+      runtime = {
+        version = 'LuaJIT',
+      },
+      workspace = {
+        preloadFileSize = 10000,
+        library = {
+          vim.env.VIMRUNTIME,
+        }
+      },
+    },
+  },
+}
+
+vim.lsp.config('lua_ls', config)
+```
+
+## Troubleshooting
+
+Start with `:checkhealth vim.lsp` to troubleshoot. The most common reasons a language server does not start or attach are:
+
+1. Language server is not installed. nvim-lspconfig does not install language servers for you. You should be able to run the `cmd` defined in the config from the command line and see that the language server starts. If the `cmd` is a name instead of an absolute path, ensure it is on your `$PATH`.
+2. Missing filetype plugins. Some languages are not detected by Nvim because they have not yet been added to the filetype detection system. Ensure `:set filetype?` shows the filetype and not an empty value.
+3. Not triggering root detection. Some language servers require a "workspace", which is found by looking for an ancestor directory that contains a "root marker". The most common root marker is `.git/`, but each config defines other "root marker" names. Root markers/directories are listed in `:help lspconfig-all`.
+
+   You can also explicitly set a root instead of relying on automatic detection by enabling `'exrc'` and adding an `.nvim.lua` at the desired root dir with the following code:
+   ```lua
+   vim.lsp.config('<client name>', {
+     root_dir = vim.fn.fnamemodify(debug.getinfo(1, 'S').source:sub(2), ':p:h'),
+   })
+   ```
+   Note that prior to nvim 0.12 `exrc` file is executed only if it's inside of a cwd where you start `nvim`.
+
+## Bug reports
+
+If you found a bug with LSP functionality, [report it to Neovim core](https://github.com/neovim/neovim/issues/new?assignees=&labels=bug%2Clsp&template=lsp_bug_report.yml).
+
+Before reporting a bug, check your logs and the output of `:checkhealth vim.lsp`. Add this to your init.lua to enable verbose logging:
+
+```lua
+vim.lsp.log.set_level('debug')
+```
+
+Attempt to run the language server, then run `:LspLog` to open the log.
+Most of the time, the reason for failure is present in the logs.
+
+## Contributions
+
+If a language server is missing from [configs.md](doc/configs.md), contributing
+a new configuration for it helps others, especially if the server requires special setup. Follow these steps:
+
+1. Read [CONTRIBUTING.md](CONTRIBUTING.md).
+2. Create a new file at `lsp/<server_name>.lua`.
+    - Copy an [existing config](https://github.com/neovim/nvim-lspconfig/tree/master/lsp)
+      to get started. Most configs are simple. For an extensive example see
+      [texlab.lua](https://github.com/neovim/nvim-lspconfig/blob/master/lsp/texlab.lua).
+3. Ask questions on [GitHub Discussions](https://github.com/neovim/neovim/discussions) or in the [Neovim Matrix room](https://app.element.io/#/room/#neovim:matrix.org).
+
+## Release process
+
+To publish a release:
+
+- Create and push a new [tag](https://github.com/neovim/nvim-lspconfig/tags).
+- After pushing the tag, a [GitHub action](./.github/workflows/release.yml)
+  will automatically package the plugin and publish the release to LuaRocks.
+
+## License
+
+Copyright Neovim contributors. All rights reserved.
+
+nvim-lspconfig is licensed under the terms of the Apache 2.0 license.
+
+See [LICENSE.md](./LICENSE.md)