aboutsummaryrefslogtreecommitdiffstats
path: root/scripts
Commit message (Collapse)AuthorAgeFilesLines
* fix(docs): handle config errors, document rename #4192Justin M. Keyes2025-11-161-4/+22
| | | | | | | | | | | | | | | Problem: If a config throws an error it fails the entire doc generation. Solution: Handle config error in docgen. Unfortunately, this doesn't show the error message, it shows: loop or previous error loading module 'lsp.volar' instead of the actual `error('…')` message. So meanwhile, document the current deprecation/rename pattern and use `vim.notify()` instead.
* fix(docs): "commands" item breaks docgen #3944Fidel Yin2025-07-101-4/+1
|
* feat(docgen.lua): convert `@brief` codeblocks for vimdoc #3787Justin M. Keyes2025-04-261-4/+33
|
* feat(docgen.lua): improve vimdoc generator #3783Justin M. Keyes2025-04-261-12/+13
|
* fix(docgen.lua): obsolete enable snippetJustin M. Keyes2025-04-251-1/+1
|
* fix(docgen.lua): omnisharp "--hostPID" arg always changes #3763Justin M. Keyes2025-04-221-58/+85
|
* ci(lint): use client:exec_cmd() #3755Justin M. Keyes2025-04-211-2/+1
| | | | Use `client:exec_cmd()` instead of calling `request("workspace/executeCommand")` directly.
* fix(docs): docgen.lua reads from `lua/*.lua` #3708Justin M. Keyes2025-04-122-144/+53
| | | | | | | | 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.
* refactor: replace vim.loop with vim.uv #3703v2.0.0Chris Bandy2025-04-101-4/+4
| | | | | | The former is deprecated in neovim 0.10. Remove the check added in 9b89ba5f158f73779cd58d0bb2783dfb40b28b0e. See: https://github.com/neovim/neovim/blob/v0.10.0/runtime/doc/deprecated.txt#L55
* fix(docgen): :help (vimdoc) format #3683Justin M. Keyes2025-04-023-25/+18
| | | followup to #3675
* fix(docgen): generate configs.txt in :help (vimdoc) format #3675Daigo Yamashita2025-04-022-18/+54
|
* fix(docgen): root_dir doc shows paths from CI env #3630Justin M. Keyes2025-02-271-1/+1
| | | | | | | | | | | | | Problem: When `root_dir` is not defined as a function, the generated docs show the paths resolved in the CI env: root_dir : lua "/home/runner/work/nvim-lspconfig/nvim-lspconfig" Solution: Always show the "gF" message for `root_dir`, even if it is not a function. Fix #3628
* refactor(docgen): use vim.text.indent() #3629Justin M. Keyes2025-02-271-15/+1
|
* build: remove `docgen.sh`dundargoc2025-01-212-9/+15
| | | | Instead, generate documentation by running the `docgen.lua` executable.
* refactor: silence luals warningsdundargoc2024-12-221-2/+2
|
* refactor: deprecate util.path.joindundargoc2024-12-211-1/+1
| | | | Work on https://github.com/neovim/nvim-lspconfig/issues/2079.
* refactor: fix luals warningsv1.2.0dundargoc2024-12-191-4/+3
|
* Revert "refactor: use simpler file existence check" #3495Justin M. Keyes2024-12-061-3/+3
| | | | | This reverts commit 90c1c6cc822b1836209514c096069b9bbeab63d9. Fix #3485
* refactor: replace all instances of vim.uv with vim.loopdundargoc2024-12-021-3/+2
| | | | | We still support neovim 0.9 currently, so we can't use vim.uv. Also add a check so we don't accidentally reintroduce it.
* refactor: use simpler file existence checkdundargoc2024-12-011-3/+3
| | | | | The vimscript function `getftype` is an easier way to check for file existence compared to vim.uv.
* refactor: deprecate util.path.is_file #3474dundargoc2024-11-281-3/+3
|
* feat(docs): improve formatting of generated docs #3400Justin M. Keyes2024-10-241-18/+13
|
* feat(docs): improve formatting of generated docsJustin M. Keyes2024-10-241-9/+6
|
* feat(docs): autogenerate default_config docsJustin M. Keyes2024-10-241-22/+22
| | | | | | | | | Problem: debug.info() is useless for some functions because they point to util.lua Solution: Provide a path to the source code instead of trying to inline the source code.
* feat(docs): autogenerate default_config docsJustin M. Keyes2024-10-241-6/+29
| | | | | | | | | Problem: Docs are manually maintained everywhere for no good reason. Solution: - revert commit 9dc02492c4a457479f8a0ec7a65aac1852ff59c0 - provide a "gF" friendly link to the source
* docs: fix old URLJustin M. Keyes2024-10-091-1/+1
|
* refactor: minor cleanupJustin M. Keyes2024-10-061-8/+8
|
* ci: rename README_template.md #3357Justin M. Keyes2024-10-062-1/+1
| | | | The name `README_template.md` is confusing, because it is not related to the README (that changed long ago).
* docs: hide modeline #3356Jan Fooken2024-10-061-0/+2
|
* refactor(docgen): cleanup #3336Justin M. Keyes2024-10-021-13/+16
|
* refactor: replace deprecated vim.loop with vim.uvdundargoc2024-10-021-1/+1
|
* feat: expose config definition as `config_def` #3335Justin M. Keyes2024-10-021-1/+1
| | | | | | | | | | | | | | Problem: Users/plugins may want to use the config definition without actually activating the config via setup(). Solution: - Expose `config_def` field and document it. - Also undeprecate some stuff that doesn't yet have a documented alternative. TODO: configs.lua sets `M.filetypes = config.filetypes` and other fields in ad-hoc fashion "for :LspInfo" but it's not clear when those fields are actually populated, and they don't source from `config_def`...
* refactor: rename "server_configurations" => "configs" #3330Justin M. Keyes2024-10-012-8/+8
| | | | | | | | | | | | | | Problem: The name `server_configurations` is extremely verbose and irritatingly formal and dogmatic. This overlong name is a constant nuisance when reading, writing, and coding. It's also not even correct: these configurations are just as much "client" configurations as they are "server" configurations. Solution: - Rename to a shorter name. - Leave placeholder files for any old URLs that link to the old location.
* fix(scripts): use compatible tbl_flatten in docgen (#3171)glepnir2024-05-231-9/+6
|
* refactor: add compatible tbl_flatten and lsp_get_clients for new version ↵glepnir2024-05-171-8/+10
| | | | 0.10 (#3154)
* test: remove test depend and use vusted (#2603)Raphael2023-05-111-13/+0
|
* chore: remove redundant config for Lua (#2523)Zhizhen He2023-03-231-2/+2
|
* docs: make sure username doesn't leak into generated document (#2441)figsoda2023-02-151-0/+10
| | | | | | | | | | | | | | | * docs: make sure username doesn't leak into generated document The documents previously contained `runner`, the username of GitHub Actions runners, which would be overwritten by the user's name when run locally and generate unwanted diff. * docs: rename username to user Co-authored-by: Justin M. Keyes <justinkz@gmail.com> --------- Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
* chore: use luarocks-tag-release workflowMarc Jakobi2023-02-032-14/+0
|
* ci: add luarocks upload release workflowv0.1.5Marc Jakobi2023-01-082-0/+14
| | | | | | | | | | | | The recently added rockspec (see #2307) has to be prepared and uploaded to luarocks for each release. This adds an automated workflow for it, which has been tested with plenary.nvim. To be able to upload to luarocks, the owner of the luarocks account will have to add an API key named `LUAROCKS_API_KEY` to this repo's GitHub Actions secrets.
* chore(rust-analyzer): use `vim.json.decode` instead of `fn.json_decode` (#2096)numToStr2022-08-271-1/+1
|
* docs: unverbose, mention "settings" paramJustin M. Keyes2022-06-131-3/+4
| | | | | | | | | | | | | | | | | Problem: - The docs are verbose. - The "settings" param is not really clarified anywhere. Solution: - Mention the "settings" param in the README. - Tighten up the wording. - Remove the "Use a loop to conveniently call 'setup'..." advice in the docs. It confuses users and doesn't really save much code. - Start to reduce the scope of nvim-lspconfig. - For example, it is redundant for it to document general LSP things. Thus, the help section *lspconfig-lsp* was removed. closes #1951
* docs: remove use of debug module for automatically extracting root pattern ↵Michael Lingelbach2022-03-201-16/+1
| | | | (#1799)
* docs: restore commands (#1798)Michael Lingelbach2022-03-201-9/+10
|
* docs: clean up styling in documentation (#1797)Michael Lingelbach2022-03-201-11/+12
| | | Make it more obvious not to copy/paste default_config
* fix(help): workaround plugin/users overwritting tags (#1512)Javier Lopez2021-11-302-22/+4
| | | | | | | | | | | | | Most plugin managers run :helptags in the plugin, which silently overwrites the existing doc/tags. this is an issue for us since lspconfig is manipulating the tags file to point to servers_configurations.md Instead create a markdown comment with the name of the wanted tag and make a copy in the repository of servers_configurations.md to server_configurations.txt. Now when :helptags runs it finds the txt file and generates the appropriate tag. The advantage is this solution should work in all platforms, it also removes lines from docgen CI.
* docs: make |lspconfig-server-configurations| jump to the markdown file (#1497)Michael Lingelbach2021-11-272-1/+23
| | | | | | | | | | * generating the tags at docgen and modifying the |lspconfig-server-configurations| tag allows `:help lspconfig-server-configurations` take you to ./doc/server_configurations.md * adding a modeline to the markdown file ensures it sets the correct filetype Co-authored-by: Javier López <graulopezjavier@gmail.com>
* docs: fix docgen (#1486)Michael Lingelbach2021-11-261-1/+1
|
* chore: clean up importsMichael Lingelbach2021-11-251-3/+3
|
* feat: expose configsMichael Lingelbach2021-11-251-2/+2
|
generated by cgit v1.2.3-70-g09d2 (git 2.52.0) at 2026-01-01 19:11:48 +0000