rneovim.git/test/functional/plugin/lsp, branch 20230125_mix Neovim fork with Rahm's personal hacks. fix(tests): use -l mode for lsp tests 2023-01-31T12:15:23+00:00 bfredl bjorn.linse@gmail.com 2023-01-31T12:08:46+00:00 50b256d51528fef068e07871e18aa3e324b7e2d8 This fixes "fake server" from leaking memory, which makes ASAN very upset, except on current ASAN CI for some reason. 
This fixes "fake server" from leaking memory, which makes ASAN very
upset, except on current ASAN CI for some reason.
feat(lsp): add function to clear codelens (#21504) 2022-12-31T15:16:21+00:00 Mathias Fußenegger mfussenegger@users.noreply.github.com 2022-12-31T15:16:21+00:00 6ba34e21fee2a81677e8261dfeaf24c8cd320500 Currently once you retrieve the lenses you're pretty much stuck with them as saving new lenses is additive. Adding a dedicated method to reset lenses allows users to toggle lenses on/off which can be useful for language servers where they are noisy or expensive and you only want to see them temporary. 
Currently once you retrieve the lenses you're pretty much stuck with
them as saving new lenses is additive.

Adding a dedicated method to reset lenses allows users to toggle lenses
on/off which can be useful for language servers where they are noisy or
expensive and you only want to see them temporary.
 test(lsp): add a screen:expect() between insert() and feed_command() (#21577) 2022-12-28T23:55:26+00:00 zeertzjq zeertzjq@outlook.com 2022-12-28T23:55:26+00:00 05b6dd6e5f543083ebca581506398a8c263a2db6 The insert() and feed_command() type a lot of text, with only one screen:expect() call after the feed_command() it may time out. 
The insert() and feed_command() type a lot of text, with only one
screen:expect() call after the feed_command() it may time out.
 fix(lsp): token_edit.data might be null on deletion (#21462) 2022-12-19T08:24:27+00:00 tiagovla 30515389+tiagovla@users.noreply.github.com 2022-12-19T08:24:27+00:00 f4d8e992bfcd6e9d0097b9d7a022060bd32f2069 






feat(lsp): highlight semantic token modifiers (#21390)
2022-12-12T19:43:14+00:00

Christian Clason
c.clason@uni-graz.at

2022-12-12T19:43:14+00:00

54d6a32fbdcbd5b26b72f4dca8906e60f5186d2c

Apply semantic token modifiers as separate extmarks with corresponding
highlight groups (e.g., `@readonly`). This is a low-effort PR to enable
the most common use cases (applying, e.g., italics or backgrounds on top
of type highlights; language-specific fallbacks like `@global.lua` are
also available). This can be replaced by more complicated selector-style
themes later on.




Apply semantic token modifiers as separate extmarks with corresponding
highlight groups (e.g., `@readonly`). This is a low-effort PR to enable
the most common use cases (applying, e.g., italics or backgrounds on top
of type highlights; language-specific fallbacks like `@global.lua` are
also available). This can be replaced by more complicated selector-style
themes later on.






perf(lsp): update semantic tokens algorithm for parsing modifiers (#21383)
2022-12-12T17:42:37+00:00

jdrouhard
john@drouhard.dev

2022-12-12T17:42:37+00:00

3869a2e0cf25323a8e5235840678b147ca908517

Instead of testing for every possible modifier type, only test bits up
to the highest set in the token array. Saves many bit ops and
comparisons when there are no modifiers or when the highest set bit is a
lower bit than the highest possible in the legend on average.

Can be further simplified when non-luaJIT gets the full bit module (see #21222)




Instead of testing for every possible modifier type, only test bits up
to the highest set in the token array. Saves many bit ops and
comparisons when there are no modifiers or when the highest set bit is a
lower bit than the highest possible in the legend on average.

Can be further simplified when non-luaJIT gets the full bit module (see #21222)






fix(lsp): ignore null responses for semanticTokens request (#21364)
2022-12-10T11:16:33+00:00

fsouza
108725+fsouza@users.noreply.github.com

2022-12-10T11:16:33+00:00

6d37d8cb17390419360c1459607beac2d93183b6

The spec indicates that the response may be `null`, but it doesn't
really say what a `null` response means. Since neovim raises an error if
the response is `null`, I figured that ignoring it would be the safest
bet.

Co-authored-by: Mathias Fussenegger <f.mathias@zignar.net>




The spec indicates that the response may be `null`, but it doesn't
really say what a `null` response means. Since neovim raises an error if
the response is `null`, I figured that ignoring it would be the safest
bet.

Co-authored-by: Mathias Fussenegger <f.mathias@zignar.net>






fix(lsp): followup fixes for semantic tokens support (#21357)
2022-12-09T10:54:09+00:00

jdrouhard
john@drouhard.dev

2022-12-09T10:54:09+00:00

5e6a288ce7ee079e7695525f2e9e99d071ccdfbf

1. The algorithm for applying edits was slightly incorrect. It needs to
   preserve the original token list as the edits are applied instead of
   mutating it as it iterates. From the spec:

   Semantic token edits behave conceptually like text edits on
   documents: if an edit description consists of n edits all n edits are
   based on the same state Sm of the number array. They will move the
   number array from state Sm to Sm+1.

2. Schedule the semantic token engine start() call in the
   client._on_attach() function so that users who schedule_wrap() their
   config.on_attach() functions (like nvim-lspconfig does) can still
   disable semantic tokens by deleting the semanticTokensProvider from
   their server capabilities.




1. The algorithm for applying edits was slightly incorrect. It needs to
   preserve the original token list as the edits are applied instead of
   mutating it as it iterates. From the spec:

   Semantic token edits behave conceptually like text edits on
   documents: if an edit description consists of n edits all n edits are
   based on the same state Sm of the number array. They will move the
   number array from state Sm to Sm+1.

2. Schedule the semantic token engine start() call in the
   client._on_attach() function so that users who schedule_wrap() their
   config.on_attach() functions (like nvim-lspconfig does) can still
   disable semantic tokens by deleting the semanticTokensProvider from
   their server capabilities.






feat(lsp): initial support for semantic token highlighting
2022-12-08T17:31:56+00:00

John Drouhard
john@drouhard.dev

2022-11-23T16:06:36+00:00

9f035559defd9d575f37fd825954610065d9cf96

* credit to @smolck and @theHamsta for their contributions in laying the
  groundwork for this feature and for their work on some of the helper
  utility functions and tests





* credit to @smolck and @theHamsta for their contributions in laying the
  groundwork for this feature and for their work on some of the helper
  utility functions and tests







refactor(test): create an lsp-specific helpers.lua file
2022-12-08T17:31:56+00:00

John Drouhard
john@drouhard.dev

2022-12-08T14:54:19+00:00

5e0c74cd82ce75510b15e63a1b0b51cf70cdf47f

* move the code for creating fake rpc servers there





* move the code for creating fake rpc servers there