What's New in Neovim 0.10
gpanders.com
What's New in Neovim 0.10
1–10 of 134 posts
Re: What's New in Neovim 0.10
#2Re: What's New in Neovim 0.10
#3Helix shows the way IMO but the Neovim guys are clearly not conservative.
Exciting to see the tree sitter and lsp improvements.
Re: What's New in Neovim 0.10
#4All too often I create a macro that I want to execute many times, but it's hard to know how many. I've tried the guessing approach but that has a tendency to under- or overestimate.
Re: What's New in Neovim 0.10
#5Re: What's New in Neovim 0.10
#6Re: What's New in Neovim 0.10
#7Pretty much exactly what is needed. Helix shows the way IMO but the Neovim guys are clearly not conservative. Exciting to see the tree sitter and lsp improvements.
Re: What's New in Neovim 0.10
#8Q or @ to execute a macro over all visually selected lines is a feature I didn't know about but sounds amazing. All too often I create a macro that I want to execute many times, but it's hard to know how many. I've tried the guessing approach but that has a tendency to under- or overestimate.
Re: What's New in Neovim 0.10
#9I am curious if any of the termsync options can make neovim play nicely with mosh. My dream setup is to be able to spin up preconfigured dev environments in docker containers, and use blink shell on my iPad for on the go coding. Unfortunately mosh and neovim always end up with display corruption.
They have some script that executed on login, which tried to “upgrade” my connections to mosh by downloading a static mosh bin from some server they own (so, could contain anything) and it was opt out — and lately randomly some keys just stop working on the keyboard (like, the c key just doesn’t work at all in the app).
I jumped ship to Termius, shame. How’s your experience lately?
Re: What's New in Neovim 0.10
#10I already had `K` set to LSP hover.
I just switched my comment plugin to get something LSP aware.
Hyperlinks can be a bit annoying. Because sometimes the line wraps so default terminal auto-linking doesn't work properly. Having explicit metadata will be excellent.
I already had inlay hints enabled, but they would appear at the end of the line. Having these in the right place will be fantastic.
`gx` open is not something that I was already using but I will probably start using this.