We need proper Neovim gui that is officially maintained
What's New in Neovim 0.10
11–20 of 134 posts
Re: What's New in Neovim 0.10
#12Q 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.
You might find relative line numbers useful. `set relativenumber`
Re: What's New in Neovim 0.10
#13We need proper Neovim gui that is officially maintained
What's the use case for a separate GUI for neovim? I remember using macvim for a few days maybe 8 years ago, but I never "got it". It felt like the benefits of having my editor in my terminal were thrown out for little return.
Emacs does it pretty well, one of the few things that makes me jealous of emacs as a vim user.
Re: What's New in Neovim 0.10
#14We need proper Neovim gui that is officially maintained
And I already use Neovide as a GUI pretty often.
Re: What's New in Neovim 0.10
#15Q 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
#16Re: What's New in Neovim 0.10
#17Every once in a while for the last few years I overhaul my Neovim config and try to add all the new goodies (commenting, LSP, etc., that are table stakes for most IDEs) as plugins using the latest and greatest plugin manager.
That works for a while, but like clockwork, something breaks- a plugin updates incompatibly, Neovim updates incompatibly, an external binary the plugin relies on updates incompatibly...
At this point I'm stuck with a broken IDE and I don't have the energy to debug all the moving parts. I suffer for a month or something and then restart the cycle.
For my latest config, I decided to treat Neovim and "just a text editor" and made a much smaller config ( https://github.com/bbkane/dotfiles/tree/master/nvim-03-lazy ). It's been really nice having something that "just works" for text edits and using VSCode for heavier IDE tasks.
I WANT to use Neovim for more complex tasks, but I also want a simple config that "just works".
I'm really excited that the core devs seem to agree and are adding tablestakes features to core- the new default colorscheme, Treesitter WASM, and better commenting will all make my config even simpler!
At some point I might even try LSP integration again!
Re: What's New in Neovim 0.10
#18I love seeing the development of an amazing modern replacement for Vim. I look forward to the moment where it has tons of plugins that are as easy to install as VSCode extensions are.
Re: What's New in Neovim 0.10
#19Earlier quoted context omitted.
What's the use case for a separate GUI for neovim? I remember using macvim for a few days maybe 8 years ago, but I never "got it". It felt like the benefits of having my editor in my terminal were thrown out for little return.
If neovim had a proper gui, you could move away from some of the limitations of the terminal. The biggest being using fixed width characters for drawing UI elements. Emacs does it pretty well, one of the few things that makes me jealous of emacs as a vim user.
I remember trying a terminal that didn't have fixed char widths and it mostly worked. The only real issue was line wrapping (as vim and the terminal would both wrap based on how long they considered the line to be). So maybe it would be possible! I would love to see solid support for variable-width fonts.
I know variable-width fonts are controversial, but I actually think they work well for coding but haven't had the chance to use them much due to Vim limitations. But especially for Markdown and similar mostly-text content they seem like a clear win.
Re: What's New in Neovim 0.10
#20Pretty 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.
Including more basic (as of 2024) features in the core like Helix would indeed be a good idea but would go against the existing culture of vim with many plugins competing.