this post was submitted on 16 May 2024
49 points (100.0% liked)

Neovim

2159 readers
1 users here now

founded 1 year ago
MODERATORS
top 6 comments
sorted by: hot top controversial new old
[–] [email protected] 3 points 5 months ago (2 children)

Lots of breaking changes. It seems like all of the changes are breaking something according to these release notes.

[–] [email protected] 13 points 5 months ago (1 children)

Also my CPU now longer overheats when holding space. WTF?

[–] [email protected] 3 points 5 months ago
[–] [email protected] 2 points 5 months ago* (last edited 5 months ago)

One breaking change, that they doesn't list as breaking (I guess since I assume the old was always broken) is: Dynamic registration of LSP capabilities. An implication of this change is that checking a client's server_capabilities is no longer a sufficient indicator to see if a server supports a feature. Instead use client.supports_method(). It considers both the dynamic capabilities and static server_capabilities.

So if you had code like

if client.server_capabilities.inlayHintProvider then
...
end

you now should use

if client.supports_method("inlayHintProvider") then
...
end

So, not really a breaking change I guess, but something you should change any way.

[–] sxwpb 3 points 5 months ago

new disable foldtext option is cool

[–] [email protected] 3 points 5 months ago

:lua with a [range] executes that range as Lua code, in any buffer.

Finally! Something similar to M-x eval-region built-in (as far as I'm aware).