aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim
Commit message (Collapse)AuthorAge
* lsp: Use incremental sync by defaultMathias Fussenegger2021-03-11
| | | | | | | | | With the new implementation added in https://github.com/neovim/neovim/pull/14079 I think this is now working well enough to enable it by default. There are high CPU usage issues popping up now and then and they might at least partially be related to the full-text sync.
* Merge pull request #14073 from mjlbach/feature/syntax_highlight_ruleMichael Lingelbach2021-03-10
|\ | | | | lsp: add custom syntax rule for floating window
| * lsp: add custom syntax rules for lsp floating windowMichael Lingelbach2021-03-09
| |
* | lsp: Resolve codeLense server capabilities (#14056)Josa Gesell2021-03-10
| |
* | lsp: get_language_id (#14092)TJ DeVries2021-03-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Allow specifying a languageId for a lsp For some languages the filetype might not match the languageId the language server accepts. In these cases the config for the language server can contain a function which gets the current buffer and filetype and returns a languageId. When it isn't provided the filetype is used instead. Example: ```lua require'lspconfig'.sourcekit.setup{ get_language_id = function(bufnr, ft) return 'swift' end; } ``` Closes #13093 * lsp: Change to get_language_id Co-authored-by: Jan Dammshäuser <mail@jandamm.de>
* | lsp: fix endline such that it cannot point outside the buffer rangeMichael Lingelbach2021-03-10
| |
* | lsp: add incremental text synchronizationMichael Lingelbach2021-03-09
| | | | | | | | | | * Implementation derived from and validated by vim-lsc authored by Nate Bosch
* | Merge pull request #13993 from teto/gendocMatthieu Coudron2021-03-07
|\ \ | |/ |/| improve vimdoc generation
| * chore: rename progress_callback to progress_handlerMatthieu Coudron2021-03-04
| |
* | Merge pull request #13919 from TheAlakazam/lsplogfixMichael Lingelbach2021-03-06
|\ \ | | | | | | fix: fix empty line in lsp log after each run
| * | lsp: add explicit entry on lsp log startPiyush Jaipuriyar2021-03-06
| | | | | | | | | | | | fix: address typo and review comments
* | | Merge pull request #13793 from mjlbach/fix_terminating_eol_diagnosticMichael Lingelbach2021-03-05
|\ \ \ | | | | | | | | [RDY] lsp: fix diagnostic reported on terminating EOL character
| * | | lsp: fix diagnostic reported on terminating EOL characterMichael Lingelbach2021-03-02
| | |/ | |/|
* | | lsp: don't invoke vim.notify on sigterm of language serverMichael Lingelbach2021-03-04
| | |
* | | lsp: invoke vim.notify when client exits with code or signal other than 0Michael Lingelbach2021-03-04
|/ /
* | fix: show error when language server start fails and prevent future requestsDavid Zhang2021-02-26
| |
* | LSP: Resolve text_document_save capability according to specMathias Fussenegger2021-02-25
| | | | | | | | | | Fixes https://github.com/neovim/neovim/issues/13989 See https://github.com/microsoft/language-server-protocol/issues/288
* | [LSP] Add in more docs for highlight groups with document_highlight() (#13614)Chris Kipp2021-02-24
| | | | | | | | | | | | Currently it's not 100% clear that without setting these, using the autocomds to utilize the `textDocument/documentHighlight` functionality, nothing will actually be visible since the highlight groups don't have any details. This just adds in a couple simple extra notes to make sure that's done
* | fix: treesitter languagetree crash when using telescope buffer previewer ↵Simon Hauser2021-02-23
| | | | | | | | (#13986)
* | lsp: remove deprecated references to 'callbacks' (#13945)Matthieu Coudron2021-02-23
| | | | | | | | | | vim.lsp.callbacks was deprecated a few months ago. This is a cleanup before the release. Use vim.lsp.handlers instead.
* | feat(lsp): use vim.notify for some errors (#13992)Matthieu Coudron2021-02-22
| |
* | lsp: Fix text edits operating on the last line of a document (#13677)Mathias Fußenegger2021-02-19
| | | | | | | | | | | | `lines` can be empty, in which case `#lines[#lines]` failed with an error: lsp/util.lua:214: attempt to get length of a nil value
* | lsp: client stop cleanups (#13877)Michael Lingelbach2021-02-19
|/ | | | | | | | * lsp: client stop cleanups * Add diagnostic clearing to client.stop() method used by nvim-lspconfig * Clear diagnostic cache to prevent stale diagnostics on client restart * lsp: Add test for vim.lsp.diagnostic.reset
* buffer updates: add on_reload callback and handle it in treesitter parserBjörn Linse2021-02-10
|
* treesitter: propagate on_detach event properlyBjörn Linse2021-02-10
|
* Merge pull request #13843 from teto/notif_providerMatthieu Coudron2021-02-08
|\ | | | | [RDY] Notification provider
| * feat: adds vim.notifyMatthieu Coudron2021-01-31
| | | | | | | | | | | | | | | | | | | | | | | | | | Adds function to notify the user like this: `:lua vim.notify("hello user")` embeds log levels vim.log.levels. you can then reassign vim.notify to for instance ``` function notify_external(msg, log_level, opts) vim.fn.jobstart({"notify-send", msg }) end ```
* | treesitter: small fixesSantos Gallegos2021-02-07
| | | | | | | | Mostly typos I found while reading the code.
* | lsp: Fix pumvisible() check introduced in #12900 (#13866)runiq2021-02-04
|/ | | | | | | | `pumvisible()` returns a number, and numbers are always `true` in Lua, so the return value needs to be checked explicitly. Using https://github.com/neovim/neovim/pull/12900 as context, it appears the intention was to move into the `if` branch when the completion popup is not shown (i.e. `vim.fn.pumvisible() == 0`).
* lsp: match textDocument/didChange eol behavior (#13792)Michael Lingelbach2021-01-25
| | | We should be consistent in sending the EOL character to servers(I think). Julia expects this to match on bufwrite, or it crashes when vim appends the newline during the write process.
* lsp: clear diagnostics on client shutdown (#13788)Michael Lingelbach2021-01-23
|
* fix(languagetree): use tree nodes instead of regions in containsSteven Sojka2021-01-20
|
* Merge pull request #13765 from jvgrootveld/ts-default-start-end-row-on-captureThomas Vigouroux2021-01-20
|\ | | | | treesitter: default start and end row when omitted
| * treesitter: Fix linter warning and add helper function to remove duplicated ↵“jvgrootveld”2021-01-18
| | | | | | | | | | | | | | logic This function returns the start and stop value if set else the node's range is used When the node's range is used, the stop is incremented by 1 to make the search inclusive
| * treesitter: default start and end row when omitted“jvgrootveld”2021-01-15
| | | | | | | | | | | | | | | | | | | | | | Add support for default start and end row when omitted in the query:iter_captures and query:iter_matches functions. When the start and end row values are omitted, the values of the given node is used. The end row value is incremented by 1 to include the node end row in the match. Updated tests and docs accordingly.
* | lsp: remove duplicate settings validation (#13789)Michael Lingelbach2021-01-18
| |
* | lsp: validate and document server settings (#13698)Michael Lingelbach2021-01-18
| | | | | | | | * update lua documentation * run docgen
* | LSP: Fix nil settings handling in workspace/configuration (#13708)Mathias Fußenegger2021-01-18
| | | | | | | | | | | | | | | | | | The `workspace/configuration` handler could fail with the following error if `config.settings` is nil: runtime/lua/vim/lsp/util.lua:1432: attempt to index local 'settings' (a nil value)" This ensures that `config.settings` is always initialized to an empty table.
* | LSP: Add in clientInfo to initalize_params. (#13757)Chris Kipp2021-01-18
| | | | | | | | | | | | | | | | | | | | | | | | * Add in clienInfo to initalize_params. Some servers (like Metals in my case) will actually pull this info from the initalize_params and display it in the logs. I know from the server perspective it helps at times to have this available to pull from to have more details about the client and version. You can see that this is part of the spec here: microsoft.github.io/language-server-protocol/specification#initialize
* | lsp: add client/registerCapability handler (#13780)Michael Lingelbach2021-01-18
|/ | | Until we support dynamicRegistration, we should handle the client/registerCapability in core. There are still some language servers that send this request despite dynamicRegistration not being registered client-side (we got an upstream fix for the node ones, but this depends on them bumping vscode-languageserver-node).
* fix(treesitter): use source() method on attachThomas Vigouroux2021-01-14
| | | | | Fixes an issue that tree-sitter always attached to the current buffer, instead of the provided buffer.
* logging: move to XDG_CACHE_HOME (#13739)Michael Lingelbach2021-01-13
| | | | | while there is some controversy, stdpath('cache') looks like a better fit for logs than stdpath('data'): you can remove logs without preventing nvim to work which fits the XDG_CACHE_HOME definition of `user specific non-essential data files`.
* lsp: fix on_attach signature documentation (#13723)Michael Lingelbach2021-01-12
| | | * trim trailing whitespace from docs
* lsp: Add severity_limit for other diagnostics features (#13528)TJ DeVries2021-01-12
| | | | | | | | | | | * lsp: Add severity_limit for other diagnostics * docs and tests * fix: lint * Add to other types * fix: lint
* fix(lsp): Allow subsequent text document edits to pass (#13534)TJ DeVries2021-01-11
| | | | | | | * fix: Allow subsequent text document edits to pass * fixup: cleaner code * add tests
* LSP: Add diagnostic tags to client capabilities (#13578)Timmy Xiao2021-01-05
| | | pyright (possibly others) does not send any hint diagnostics if we do not have tagSupport in PublishDiagnosticsClientCapabilities. This PR just adds them.
* treesitter: simplify query reading logicBjörn Linse2021-01-04
| | | | | | | | | | | | | | Only the plugin/package manager should "manage" after/. Consumers of nvim_get_runtime_file() should not need to special case it (if your plugin manager is broken then fix it instead). Don't use vim.fn.readfile(). Lua can already read files. It is even better at it than vim script. expose M.get_query_files(). Listing the queries is essential for user config debug, and let plugins do fun things with it. Abstraction-by-obscurity is not useful (plugins can just cargo cult copy the code anyway, better with public entry points).
* LSP: fix messageRequest to not return nested title (#13674)Michael Lingelbach2021-01-03
| | | | | * LSP: fix window/showMessageRequest to not return nested title * Add window/showMessageRequest handler to docs
* Merge pull request #13649 from mjlbach/move_from_nvim-lspconfigMatthieu Coudron2021-01-01
|\ | | | | LSP: Move workspace/configuration from nvim-lspconfig to core
| * LSP: Move workspace/configuration handler from nvim-lspconfig to coreMichael Lingelbach2021-01-01
| |
generated by cgit (git 2.34.1) at 2025-06-02 11:22:43 +0000