Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Neovim v0.5

github.com

Post reply on HN
Print view View original

71–80 of 213 posts

Re: Neovim v0.5

#71

Post by epicide »

pault wrote: post #40
vogre wrote: post #34

Earlier quoted context omitted.

I would actually LOVE to see VIM with NerdTree, File/text searching, lsp and first class git support baked in and integrated well without need of tuning something in your .vimrc file every weekend.

I know it sounds snarky, but at some point of vimrc complexity it’s worth considering just switching to vscode with the vim extension. It can use neovim as a back end and you get mountains of features out of the box. I created vim-idiomatic key mappings to all the vscode features and extensions I commonly use. It’s not vim, it uses a shit ton of memory, and you can’t run it in the terminal, but I love it. For context…

I don't see this often talked about, but some of the biggest value that (n)vim provides for me is that I've configured it myself. I know what's in my .vimrc because I'm the one that put it there. It takes me longer to add new features [0], but once it is set up how I want it, I understand it more deeply.

My data is purely anecdotal but I've noticed a correlation: people who spend the added time to configure their editor (be it vim or vscode) tend to be better at using their editor. It naturally follows that the time spent configuring it leads to a better understanding (and better recall) of how it works.

In my mind, the big "omnibus" plugin bundles for (n)vim prevent that understanding just as much as a default vscode config does [1].

[0]: Either by adding a plugin or, in most cases, by incorporating what I want into (n)vim's existing systems.

[1]: And no judgement for that -- not everybody has time or patience to deeply learn every tool they use.

Re: Neovim v0.5

#72

Post by qbasic_forever »

rosetremiere wrote: post #65

I'm using neovim with Coc (often does not work as I want it to) and ALE and friends, and it's getting sort of frustrating. It's lots of fiddling with the vimrc, each year a new better extension that I can never make work, etc. What I'd like is some editor that integrates LSP, treesitter, FZF and friends so I don't have to configure everything, while still having the modal+command model of vim. Recently there was an e…

VS code + the popular vim keybinding/mode extension for its editor.

I love neovim and have been using 0.5 for 1/2 a year now, loaded up with all the bleeding edge LSP, treesitter, etc. stuff and I have come to the exact same conclusion. The ecosystem is just a bit too immature and fragile right now with tons of still-evolving things. The quality of each LSP varies wildly and it's a huge wild west right now figuring out the 'right' way to move configurations to lua, use a package manager for plugins, etc. You're left with a weird frankenstein state of half your tools and plugins in the new lua world, half still in the old world.. and a net loss of features and functionality as stuff is abandoned or changed in the process of moving. It's exhausting to keep up.

Re: Neovim v0.5

#73

Post by hkmaxpro »

rosetremiere wrote: post #65

I'm using neovim with Coc (often does not work as I want it to) and ALE and friends, and it's getting sort of frustrating. It's lots of fiddling with the vimrc, each year a new better extension that I can never make work, etc. What I'd like is some editor that integrates LSP, treesitter, FZF and friends so I don't have to configure everything, while still having the modal+command model of vim. Recently there was an e…

LunarVim: A Neovim config made with sane defaults https://github.com/ChristianChiarulli/LunarVim

LunarVim will be like Spacemacs/Doom Emacs/SpaceVim, but for neovim. A distribution of useful neovim packages with sane defaults.

This project is still at its early stage and many things change rapidly. You currently cannot easily keep your custom changes in sync with LunarVim, but support for this feature is on the way.

In a few months this project should be stable enough for typical users.

Re: Neovim v0.5

#75

Post by adkadskhj »

I really hope for one day to have Kakoune-like selection-first and multi-cursor functionality in Neovim. After moving to Kakoune i just can't go back to Vim, but Neovim's advancements make me jealous.

Congrats on 0.5, another release that looks great!

Re: Neovim v0.5

#76

Post by gen220 »

prince781 wrote: post #52
gen220 wrote: post #19

Is anybody else uncomfortable about the idea that an LSP client is now baked into the editor (as opposed to being a plugin)? Are there big performance gains to this approach? While LSP is great, it basically came from nowhere in the last couple of years. My concern: what if something definitively better comes along in another couple years, and we're "stuck" with this baked into the editor? For context, using ALE, I'v…

> This feels like a move away from plugins and into monolith territory, which feels like a big step. I don't consider LSP to be a monolith. You still have the decentralization of language server development. Rather, LSP is just a standardization of what we have come to expect from editors interacting with plugins. And because the standard is modular in its features, the barrier to entry for new language servers and e…

To be clear, I was saying that integrating LSP into neovim makes neovim more monolith-y than it was prior, not that LSP was a monolith! :)

Re: Neovim v0.5

#77

Post by highpost »

There is a middle ground for VS Code users:

https://github.com/asvetliakov/vscode-neovim

This extension integrates neovim into the VS Code environment by mapping keystrokes from VS Code to the neovim binary. This approach (which requires 0.5) is much simpler and more robust than attempting to emulate all of VIM, as the VSCodeVIM extension does.

Re: Neovim v0.5

#78

Post by efficax »

davidkunz wrote: post #43

I love Neovim. I switched from VSCode and never looked back, it's just so much more efficient to just do everything with your keyboard. In case someone is interested how to do the things you're used to from VSCode, I created some videos: https://youtube.com/playlist?list=PLu-ydI-PCl0OEG0ZEqLRRuCrM...

Funny, I switched from neovim to VSCode + the vim plugin. Sure, it doesn't have everything I would do with vim supported, but it's enough and overall it's a better experience

Re: Neovim v0.5

#79

Post by qbasic_forever »

highpost wrote: post #77

There is a middle ground for VS Code users: https://github.com/asvetliakov/vscode-neovim This extension integrates neovim into the VS Code environment by mapping keystrokes from VS Code to the neovim binary. This approach (which requires 0.5) is much simpler and more robust than attempting to emulate all of VIM, as the VSCodeVIM extension does.

I've always scratched my head at this plugin. Is the idea that you have both a VS code configuration for all the stuff around the editor (themes, UI stuff, all kinds of fancy VS code features like its file tree, git tree, testing, etc.), and a neovim configuration for the editor component itself? How do language servers and such work--are all the slick one click VS code installed extensions ignored and you're back to twiddling and tweaking and googling neovim config to get LSP working?

Re: Neovim v0.5

#80

Post by JasonSage »

pault wrote: post #40
vogre wrote: post #34

Earlier quoted context omitted.

I would actually LOVE to see VIM with NerdTree, File/text searching, lsp and first class git support baked in and integrated well without need of tuning something in your .vimrc file every weekend.

I know it sounds snarky, but at some point of vimrc complexity it’s worth considering just switching to vscode with the vim extension. It can use neovim as a back end and you get mountains of features out of the box. I created vim-idiomatic key mappings to all the vscode features and extensions I commonly use. It’s not vim, it uses a shit ton of memory, and you can’t run it in the terminal, but I love it. For context…

Another nice aspect of Neovim 0.5 is that you can do the entire configuration in Lua, so you can break out your config into multiple files and have things more organized and compartmentalized.
Post reply on HN