rneovim.git/runtime/lua/vim/lsp, branch userreg Neovim fork with Rahm's personal hacks. docs: support @since for api level #25574 2023-11-27T16:23:04+00:00 LW git@llllvvuu.dev 2023-11-27T16:23:04+00:00 9fa9b3cad94a1ea7fced128fed2cd5ac3ff7bc44 close #25416 
close #25416
 refactor(lsp): add type annotations to _watchfiles (#26109) 2023-11-20T16:19:41+00:00 Mathias Fußenegger mfussenegger@users.noreply.github.com 2023-11-20T16:19:41+00:00 ec79ff893d5906e1f0d90953cffa535ffae47823 






fix(lsp): advertise workspace.didChangeConfiguration capability (#26028)
2023-11-13T18:39:43+00:00

Chris Simon
chris@devcycles.io

2023-11-13T18:39:43+00:00

48bcc7b9710d6db619b05254ea87f4087cdd9764

This ensures workspace/didChangeConfiguration notification sent after init is correctly handled





This ensures workspace/didChangeConfiguration notification sent after init is correctly handled







feat(lsp)!: vim.lsp.inlay_hint.get(), enable(), is_enabled() #25512
2023-11-12T12:54:27+00:00

LW
git@llllvvuu.dev

2023-11-12T12:54:27+00:00

448907f65d6709fa234d8366053e33311a01bdb9

refactor!: `vim.lsp.inlay_hint()` -> `vim.lsp.inlay_hint.enable()`

Problem:
The LSP specification allows inlay hints to include tooltips, clickable
label parts, and code actions; but Neovim provides no API to query for
these.

Solution:
Add minimal viable extension point from which plugins can query for
inlay hints in a range, in order to build functionality on top of.

Possible Next Steps
---

- Add `virt_text_idx` field to `vim.fn.getmousepos()` return value, for
  usage in mappings of `<LeftMouse>`, `<C-LeftMouse>`, etc




refactor!: `vim.lsp.inlay_hint()` -> `vim.lsp.inlay_hint.enable()`

Problem:
The LSP specification allows inlay hints to include tooltips, clickable
label parts, and code actions; but Neovim provides no API to query for
these.

Solution:
Add minimal viable extension point from which plugins can query for
inlay hints in a range, in order to build functionality on top of.

Possible Next Steps
---

- Add `virt_text_idx` field to `vim.fn.getmousepos()` return value, for
  usage in mappings of `<LeftMouse>`, `<C-LeftMouse>`, etc






fix(lsp): create per client params in lsp.buf.code_action
2023-11-04T07:17:42+00:00

Mathias Fussenegger
f.mathias@zignar.net

2023-11-02T08:59:41+00:00

9281edb334a374e7753d4a6b7a05e31120e39772

`code_action` used the same parameters for all clients, which led to the
following warning and incorrect start/end column locations if using
clients with mixed encodings:

    warning: multiple different client offset_encodings detected for
    buffer, this is not supported yet





`code_action` used the same parameters for all clients, which led to the
following warning and incorrect start/end column locations if using
clients with mixed encodings:

    warning: multiple different client offset_encodings detected for
    buffer, this is not supported yet







fix(lsp): call `on_list()` even for single location (#25830)
2023-10-31T12:18:44+00:00

Evgeni Chasnovski
evgeni.chasnovski@gmail.com

2023-10-31T12:18:44+00:00

adbe7f368397da21465f27181e254dd3694820e9

Problem: Currently there is no way of customizing behavior of
  `declaration`, `definition`, `typeDefinition`, and `implementation`
  methods in `vim.lsp.buf` when LSP server returns `Location`. Instead,
  cursor jumps to that location directly.

Solution: Normalize LSP response to be `Location[]` for those four cases.




Problem: Currently there is no way of customizing behavior of
  `declaration`, `definition`, `typeDefinition`, and `implementation`
  methods in `vim.lsp.buf` when LSP server returns `Location`. Instead,
  cursor jumps to that location directly.

Solution: Normalize LSP response to be `Location[]` for those four cases.






fix(lsp): fix omnicomplete in middle of the line (#25787)
2023-10-26T20:40:36+00:00

Lajos Koszti
ajnasz@ajnasz.hu

2023-10-26T20:40:36+00:00

ba6761eafe615a7f904c585dba3b7d6e98f665e1

Fixes a regression from 5e5f5174e3faa862a9bc353aa7da41487911140b

Until that commit we had a logic like this:
`local prefix = startbyte and line:sub(startbyte + 1) or line_to_cursor:sub(word_boundary)`

The commit changed the logic and no longer cut off the line at the cursor,  resulting in a prefix that included trailing characters




Fixes a regression from 5e5f5174e3faa862a9bc353aa7da41487911140b

Until that commit we had a logic like this:
`local prefix = startbyte and line:sub(startbyte + 1) or line_to_cursor:sub(word_boundary)`

The commit changed the logic and no longer cut off the line at the cursor,  resulting in a prefix that included trailing characters






fix(lsp): fix off-by-one error for omnifunc word boundary
2023-10-23T06:26:38+00:00

Mathias Fussenegger
f.mathias@zignar.net

2023-10-21T11:44:53+00:00

5e5f5174e3faa862a9bc353aa7da41487911140b

Fixes https://github.com/neovim/neovim/issues/25177

I initially wanted to split this into a refactor commit to make it more
testable, but it appears that already accidentally fixed the issue by
normalizing lnum/col to 0-indexing





Fixes https://github.com/neovim/neovim/issues/25177

I initially wanted to split this into a refactor commit to make it more
testable, but it appears that already accidentally fixed the issue by
normalizing lnum/col to 0-indexing







refactor(lsp): deprecate completion util methods
2023-10-21T11:49:05+00:00

Mathias Fussenegger
f.mathias@zignar.net

2023-10-21T07:57:50+00:00

195301c60969c7ce97b1ef3a3caaf4965da1abd5

Relates to https://github.com/neovim/neovim/issues/25272





Relates to https://github.com/neovim/neovim/issues/25272







refactor(lsp): move completion logic into _completion module
2023-10-21T11:49:05+00:00

Mathias Fussenegger
f.mathias@zignar.net

2023-10-21T07:47:24+00:00

1e10310f4cc70cf95a68457c2be9e7459b5bbba6

To reduce cross-chatter between modules and for https://github.com/neovim/neovim/issues/25272
Also preparing for https://github.com/neovim/neovim/issues/25714





To reduce cross-chatter between modules and for https://github.com/neovim/neovim/issues/25272
Also preparing for https://github.com/neovim/neovim/issues/25714