rneovim.git/test/functional/plugin/lsp_spec.lua, branch fix_repeatcmdline

test: skip failing watch file tests on freebsd (#26110)

2023-11-19T17:37:49+00:00

Quick fix as follow up to https://github.com/neovim/neovim/pull/26108

kqueue only reports events on a watched folder itself, not for files
created or deleted within. So the approach the PR took doesn't work on FreeBSD.

We'll either need to bring back polling for it, combine watching with manual
file tracking, or disable LSP file watching on FreeBSD

feat(lsp)!: vim.lsp.inlay_hint.get(), enable(), is_enabled() #25512

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

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 ``, ``, etc

fix(lsp): fix off-by-one error for omnifunc word boundary

2023-10-23T06:26:38+00:00

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

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

fix(lsp): handle NUL bytes in popup text (#25612)

2023-10-12T07:39:39+00:00

Fix #25610

feat(lsp)!: replace snippet parser by lpeg grammar

2023-10-02T20:21:35+00:00

feat(lsp): fallback to code-action command on resolve failure (#25464)

2023-10-02T20:14:19+00:00

The haskell-language-server supports resolve only for a subset of code
actions. For many code actions trying to resolve the `edit` property
results in an error, but the unresolved action already contains a
command that can be executed without issue.

The protocol specification is unfortunately a bit vague about this,
and what the haskell-language-server does seems to be valid.

Example:

    newtype Dummy = Dummy Int
    instance Num Dummy where

Triggering code actions on "Num Dummy" and choosing "Add placeholders
for all missing methods" resulted in:

    -32601: No plugin enabled for SMethod_CodeActionResolve, potentially available: explicit-fields, importLens, hlint, overloaded-record-dot

With this change it will insert the missing methods:

    instance Num Dummy where
      (+) = _
      (-) = _
      (*) = _
      negate = _
      abs = _
      signum = _
      fromInteger = _

fix(lsp): handle absence of a trailing newline #25194

2023-09-21T10:06:40+00:00

Fixes #24339

rust-analyzer sends "Invalid offset" error in such cases. Some other
servers handle it specially.

LSP spec mentions that "A range is comparable to a selection in an
editor". Most editors don't handle trailing newlines the same way
Neovim/Vim does, it's clearly visible if it's present or not. With that
in mind it's understandable why sending end position as simply the start
of the line after the last one is considered invalid in such cases.

feat(lsp): use treesitter for stylize markdown

2023-09-19T13:47:37+00:00

fix(api): more intuitive cursor updates in nvim_buf_set_text

2023-09-11T04:16:03+00:00

Fixes #22526