Earlier quoted context omitted.
Coc works with Neovim too if that's the logic.
I know, but previously, the inlay hints would be displayed at the end of the line in Neovim, making them near useless.
Huh, does it work inline in Vim with Coc?
What's New in Neovim 0.10
91–100 of 134 posts
Re: What's New in Neovim 0.10
#92The ultimate proof that Neovim has a healthy team of contributors, is that they successfully agreed on a new default color scheme. I am now convinced they can succeed with anything.
The proposal from a brave soul: https://github.com/neovim/neovim/pull/26334
Re: What's New in Neovim 0.10
#93Every ~6 months I try to switch from vim to nvim, but somehow it never sticks. Not sure why but in my use cases it is slower than vim, the terminal is imo still worse than vim and it s harder to copy and paste to the terminal: in vim I yank and than C_W"0 (or whatever register I need) in nvim I didn't find a solution yet. Nvim always feels more clunky.
Re: What's New in Neovim 0.10
#94Neovim is great and is my daily driver for a couple of years now. I was really looking forward to 0.10 because the roadmap said "multicursor", and that's the only thing that sometimes make me open Sublime Text, but it seems like it was more complex to implement than originally estimated and so it was now pushed to 0.12 ( https://neovim.io/roadmap/ ).
What's the difference between multicursor and visual block? Genuinely curious, is it that things don't have to be vertically aligned? What's the ux expectation in a pure keyboard based workflow?
Re: What's New in Neovim 0.10
#95Re: What's New in Neovim 0.10
#96Am I the only one who doesn't like the new color scheme that much? It seems that it just plainly removes all the syntax highlighting more or less.
Functionally it's good - adapts to both light and dark background, adapts to both 256 and truecolor terminals. I think I miss some of the color even if bright color in light background themes is often detrimental. Only real dislike is the too gray tinted background. Should be more towards white for light background, to be more neutral.
Re: What's New in Neovim 0.10
#97When I first started to learn how to program I was following along a basic tutorial by Jeffrey Way and his first sentence was "We're going to use vim." That tutorial, whose topic I can't even remember now, set me on a path for my professional career. During 2012-2015 there seemed to be way more competition in the editor space before VS Code gobbled the community mindshare. I remember starting my first professional jo…
> because he used emacs and wanted to argue with someone about emacs in the office That's weird to me as in more than 20+ years I don't think I've ever been around people arguing that in real life. It's always been more of a meme to me than anything real.
It was always good natured and I enjoyed the comradery that came from it. He also taught me a lot about vim and command line tools in general.
Re: What's New in Neovim 0.10
#98The ultimate proof that Neovim has a healthy team of contributors, is that they successfully agreed on a new default color scheme. I am now convinced they can succeed with anything.
Next up, tabs vs spaces!!!
Re: What's New in Neovim 0.10
#99Am I the only one who doesn't like the new color scheme that much? It seems that it just plainly removes all the syntax highlighting more or less.
you might want to try linking @variable to Identifier, i think the original author decided to keep @variable unhighlighted to keep the color diff between having `termguicolors` on/off to a minimum (Identifier assumes `termguicolors` is enabled, but for default colorscheme it's likely not always the case).
see https://github.com/neovim/neovim/pull/26334 and the comments in highlight_group.c
Re: What's New in Neovim 0.10
#100Neovim is great and is my daily driver for a couple of years now. I was really looking forward to 0.10 because the roadmap said "multicursor", and that's the only thing that sometimes make me open Sublime Text, but it seems like it was more complex to implement than originally estimated and so it was now pushed to 0.12 ( https://neovim.io/roadmap/ ).
Noticed this also. Truly the only reason I still open up vscode. And repo find / replace. Otherwise Switched to nvim full time about 5 months ago, can do everything and more ha
https://github.com/nvim-pack/nvim-spectre
Is a great find and replace plugin for your repo.
so is quick fix list + `:cdo s//gc | :cdo update`