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

151–160 of 213 posts

Re: Neovim v0.5

#151

Post by akkartik »

ufo wrote: post #150
luke2m wrote: post #21

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

One small thing I prefer about neovim is that the default settings are better. For example, syntax highlighting is enabled. https://neovim.io/doc/user/vim_diff.html#vim-differences

That's actually a negative for an existing user like me. Every time I upgraded to Neovim I ran into breakage with my configuration. Eventually I burned out and returned to Vim.

Neovim may well be taking the right approach. Capture by existing users has its own costs. But we should be clear-eyed about its intended audience.

Re: Neovim v0.5

#152

Post by muststopmyths »

systems wrote: post #132
junon wrote: post #106

Earlier quoted context omitted.

Neovim has plugins...

I am not sure I fully grasp this yet but comments above are suggesting that because of LSP (Language server protocols) plugins can be portable now, from one editor to another i thought each editor needed its own plugin, and VS Code always seem to have the main plugin, didnt really come across plugins that run across multiple editor, but then i was not really checking this, next time i will check it

It's not that plugins are portable. LSP allows any editor that supports the protocol to provide language support (using a backend "language server" that is editor-agnostic), so it is not that hard for most editors these days to provide good intellisense/syntax-highlighting etc. that used to be limited to commercial-grade IDEs.

Re: Neovim v0.5

#153

Post by bunnyfoofoo »

toxik wrote: post #126
MaxBarraclough wrote: post #25

Earlier quoted context omitted.

For anyone else wondering: • LSP means Language Server Protocol [0] • ALE means Asynchronous Lint Engine [1] [0] https://microsoft.github.io/language-server-protocol/ [1] https://github.com/dense-analysis/ale

ALE is amazingly useful even for curmudgeonly old timer Vim users. My one gripe is that I want the warnings to disappear once I begin modifying the buffer, which I have achieved. Can post the relevant part of my vimrc if desired.

I’d like to see that as well, please.

Re: Neovim v0.5

#154

Post by EvanDotPro »

Jenk wrote: post #85
efficax wrote: post #78

Earlier quoted context omitted.

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

I've started using the vscode neovim plugin. It runs a headless neovim in the background so you get literally everything that both editors provide in one. It's not 100% flawless but it is damn good. I used to flip between the two anyway - if I needed a better intellisense for, say, a large typescript project, then vscode won, everything else was nvim. Now I have the intellisense of vscode ontop of neovim.

As a LONG time Vim (now Neovim) user, I've been pretty curious to try this as it would allow me to retain some of my beloved plugins and custom config without the effort of trying to find replacements or reproduce my config stuff. I imagine I could also get rid of most of the language server / autocomplete / code navigation type stuff that comes easier in VS code. It could potentially be the best of both worlds if it's done as well as I'm hoping it is.

I haven't tried it yet, but my main concern is that VS Code probably has a lot of keyboard shortcuts (e.g., C-v for visual block mode) that I'd have to reassign, which could potentially be a bit of a pain initially.

Mind sharing any pros/cons you've run into with the Neovim plugin so far?

Re: Neovim v0.5

#155

Post by lordgroff »

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

I'd love to go back to (neo)vim. I like vscode fine, but sometimes it sounds like a rocket is taking off from my laptop. However, the ability to have a full remote development environment act pretty much exactly like the local one is the absolute vscode killer feature. I just can't go back to a ssh season, cloning the plugins, and dealing with occasional latency.

Re: Neovim v0.5

#156

Post by robryan »

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.

Yeah LSP also makes Sublime viable going forward where it otherwise probably would have fallen behind.

Re: Neovim v0.5

#157

Post by liveranga »

EvanDotPro wrote: post #154
Jenk wrote: post #85

Earlier quoted context omitted.

I've started using the vscode neovim plugin. It runs a headless neovim in the background so you get literally everything that both editors provide in one. It's not 100% flawless but it is damn good. I used to flip between the two anyway - if I needed a better intellisense for, say, a large typescript project, then vscode won, everything else was nvim. Now I have the intellisense of vscode ontop of neovim.

As a LONG time Vim (now Neovim) user, I've been pretty curious to try this as it would allow me to retain some of my beloved plugins and custom config without the effort of trying to find replacements or reproduce my config stuff. I imagine I could also get rid of most of the language server / autocomplete / code navigation type stuff that comes easier in VS code. It could potentially be the best of both worlds if it…

I've been using it for a couple months now. It's really quite good and the plugin disables most (all?) of the clashing hotkeys.

The only thing I've noticed is sometimes there's a delay on the Esc key detection to exit insert mode. That could be my binding of CapsLock to Esc/Ctrl though (with a combination of xmodmap and xcape).

I'm also a long time vim user but this has made it bearable to use the same editor as the rest of the team (engineers who need to code, not software engineers) so that they understand what's happening when pair programming etc.

Re: Neovim v0.5

#158

Post by jay-aye-see-key »

EvanDotPro wrote: post #154
Jenk wrote: post #85

Earlier quoted context omitted.

I've started using the vscode neovim plugin. It runs a headless neovim in the background so you get literally everything that both editors provide in one. It's not 100% flawless but it is damn good. I used to flip between the two anyway - if I needed a better intellisense for, say, a large typescript project, then vscode won, everything else was nvim. Now I have the intellisense of vscode ontop of neovim.

As a LONG time Vim (now Neovim) user, I've been pretty curious to try this as it would allow me to retain some of my beloved plugins and custom config without the effort of trying to find replacements or reproduce my config stuff. I imagine I could also get rid of most of the language server / autocomplete / code navigation type stuff that comes easier in VS code. It could potentially be the best of both worlds if it…

I started with vscode but moved to (neo)vim 2 or 3 years ago. Last year I experimented going back to vscode with one of the vim plugins.

By default there are some conflicting keybinds like ctrl-o and ctrl-v, but these can be disabled in vscode settings.json so wasn’t a problem.

The main feature that doesn’t work over the neovim-vscode rpc bridge is undo tree, that was important to me. You also have to put up with much slower start up times and slower syntax highlighting because vscode uses lsp highlighting.

But the deal breaker for me was losing any vim plug-in with a ui component like fzf, fugitive, and the file tree I like (fern.vim).

It might work for you, some coworkers switched from vim to vscode-neovim and were very happy with the compromise.

Re: Neovim v0.5

#159

Post by root_axis »

_benj wrote: post #10

For those out there trying to "learn" vim, give neovim 0.5 a try! I've been using neovim HEAD (0.5 pre-release) for a while and it has been awesome. It all started with this config [0] and from there and haven't tried (as before) to join a vim cult but instead to use it as a tool that works for me (i.e. use mouse scroll to browse around, use arrows on insert mode, and other vim sins) Little by little I've been lookin…

I always pick up great tips in these threads... 0p is the latest, thanks!

Re: Neovim v0.5

#160

Post by junon »

systems wrote: post #132
junon wrote: post #106

Earlier quoted context omitted.

Neovim has plugins...

I am not sure I fully grasp this yet but comments above are suggesting that because of LSP (Language server protocols) plugins can be portable now, from one editor to another i thought each editor needed its own plugin, and VS Code always seem to have the main plugin, didnt really come across plugins that run across multiple editor, but then i was not really checking this, next time i will check it

Most Vim plugins work unmodified on Neovim.
Post reply on HN