aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/strings.c
diff options
context:
space:
mode:
authorMathias Fußenegger <mfussenegger@users.noreply.github.com>2023-06-09 11:32:43 +0200
committerGitHub <noreply@github.com>2023-06-09 11:32:43 +0200
commite5e0bda41b640d324350c5147b956e37e9f8b32c (patch)
treed546e647fcde46494740852171593e78101d9997 /src/nvim/strings.c
parentf31dba93f921891159eb707b185517648df00d6b (diff)
downloadrneovim-e5e0bda41b640d324350c5147b956e37e9f8b32c.tar.gz
rneovim-e5e0bda41b640d324350c5147b956e37e9f8b32c.tar.bz2
rneovim-e5e0bda41b640d324350c5147b956e37e9f8b32c.zip
feat(lsp)!: add vim.lsp.status, client.progress and promote LspProgressUpdate (#23958)
`client.messages` could grow unbounded because the default handler only added new messages, never removing them. A user either had to consume the messages by calling `vim.lsp.util.get_progress_messages` or by manually removing them from `client.messages.progress`. If they didn't do that, using LSP effectively leaked memory. To fix this, this deprecates the `messages` property and instead adds a `progress` ring buffer that only keeps at most 50 messages. In addition it deprecates `vim.lsp.util.get_progress_messages` in favour of a new `vim.lsp.status()` and also promotes the `LspProgressUpdate` user autocmd to a regular autocmd to allow users to pattern match on the progress kind. Also closes https://github.com/neovim/neovim/pull/20327
Diffstat (limited to 'src/nvim/strings.c')
0 files changed, 0 insertions, 0 deletions