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

111–120 of 213 posts

Re: Neovim v0.5

#111

Post by qudat »

davidkunz wrote: post #98
systems wrote: post #87

Earlier quoted context omitted.

I am not sure how this is possible Editors like Vim, Emacs or VSCode are all about the plugins I use emacs for org mode And VSCode for everything else, because simply most proramming languages have their main plugins on VSCode The only way you can move from VSCode to neovim is, if you dont care about the plugins Why would you VSCode if not for the plugins

Regarding programming languages, the answer is the language server protocol (LSP), an editor-agnostic way to use IDE-like features, originally developed for VSCode. Works for both Neovim and VSCode (and many others). Somewhat ironic that one of VSCode's best inventions is the one which made me switch away from it.

I just switched from 0.4 to 0.5 specifically for LSP and treesitter support. There is zero difference between it and vscode for me now. Neovim 0.5 is a game changer and closes the gap between it and vscode.

Re: Neovim v0.5

#113

Post by njharman »

humility wrote: post #29
luke2m wrote: post #21

Could someone sell me on why I should switch to this from regular Vim?

lots of stuff. but mainly: * ease of getting started. nvim is just vim, you can bring over your vim config and it'll just work. * integrated lsp. you could have vscode like auto completion natively * tree-sitter. google it to believe it and much, much more

My vim config includes bunch of customization for bunch of plugins written in vimscript. Will that just work?

Re: Neovim v0.5

#114

Post by ibraheemdev »

One little-talked about advantage of Lua support is that you can now write your vim config/scripts in one of the various Lua transpilers like moonscript [0], or maybe even typescript [1]!

[0]: https://github.com/leafo/moonscript

[1]: https://github.com/TypeScriptToLua/TypeScriptToLua

[2]: https://github.com/hengestone/lua-languages

Re: Neovim v0.5

#115

Post by CameronNemo »

shiryel wrote: post #100
systems wrote: post #87

Earlier quoted context omitted.

I am not sure how this is possible Editors like Vim, Emacs or VSCode are all about the plugins I use emacs for org mode And VSCode for everything else, because simply most proramming languages have their main plugins on VSCode The only way you can move from VSCode to neovim is, if you dont care about the plugins Why would you VSCode if not for the plugins

Well, mostly of the language specific plugins are language server protocols (LSP), you only need a client to make they work on any editor, I used to use CoC on vim to have that power, but now with the new version of NeoVim the client is build-in, so...

now with the new version of NeoVim the client is built-in

Can you link me to how to configure that? I have been using LanguageClient-neovim, which is a Rust plugin.

Re: Neovim v0.5

#116

Post by kellyjprice »

njharman wrote: post #113
humility wrote: post #29

Earlier quoted context omitted.

lots of stuff. but mainly: * ease of getting started. nvim is just vim, you can bring over your vim config and it'll just work. * integrated lsp. you could have vscode like auto completion natively * tree-sitter. google it to believe it and much, much more

My vim config includes bunch of customization for bunch of plugins written in vimscript. Will that just work?

Probably. I have not had any problems switching between the two. It's meant to be a drop in replacement, but I'm not sure how perfect that is.

Re: Neovim v0.5

#117

Post by coldtea »

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…

>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?

LSP is not going anywhere. Nor has it been here just for a "couple of years". It's here for over 5 years already.

Re: Neovim v0.5

#119

Post by jpe90 »

In my experience, the built in LSP is a mixed bag. Getting language servers configured is a breeze, diagnostics and go-to definition work just fine. But trying to get autocomplete and snippets to work is an exercise in frustration. There's a handful of different hobbyist implementations which are all somewhat-maintained and somewhat work together but it's buggy and you end up needing to do 20x the effort of using VS code to get not quite the same ease of use.

I really hope they'll do some official work on lua-based solutions for autocomplete and code snippets in the future to really round out the LSP support, if that's something that they want to highlight as a feature of neovim. I still think VS code is the way to go if you want LSP features, but 0.5 is a terrific step forward and everyone who worked on it should be very proud.

Re: Neovim v0.5

#120

Post by davidkunz »

CameronNemo wrote: post #115
shiryel wrote: post #100

Earlier quoted context omitted.

Well, mostly of the language specific plugins are language server protocols (LSP), you only need a client to make they work on any editor, I used to use CoC on vim to have that power, but now with the new version of NeoVim the client is build-in, so...

now with the new version of NeoVim the client is built-in Can you link me to how to configure that? I have been using LanguageClient-neovim, which is a Rust plugin.

I talked about the configuration in my videos (linked above).

The best place to start is here: https://github.com/neovim/nvim-lspconfig

I use it in combination with nvim-compe: https://github.com/hrsh7th/nvim-compe

Post reply on HN