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

Neovim v0.4.0

github.com

Post reply on HN
Print view View original

151–160 of 168 posts

Re: Neovim v0.4.0

#151

Post by L0stLink »

blux wrote: post #150
L0stLink wrote: post #106

Earlier quoted context omitted.

I have been using LanguageClient-neovim[0]. It is great, the main difference I have observed between LanguageClient-neovim and coc.vim is that LanguageClient-neovim provides a more vim centered UX (e.g. it automatically populates location/quickfix list with errors, warnings and hints which enables quickly jumping between error locations) while coc.vim provides a great out-of-the box experience but feels like VSCode s…

Thank you for the elaborate answer, seems like LanguageClient-neovim will be a perfect fit!

No problem, LanguageClient-neovim can be a bit overwhelming at first and if you are like me, you might need to rely on the included docs and GitHub issues, but it is well worth it. I am in my spare time working on getting floating window documentation working for completion items once that is done, I will have no need to keep coc.vim installed as backup.

Re: Neovim v0.4.0

#152

Post by linsomniac »

Aissen wrote: post #136
NilsIRL wrote: post #132

Earlier quoted context omitted.

Why are you still using VIM if you like Neovim's features? (this is not a rhetorical question)

Never attempted to make the move (friction, sizeable vimrc). I've mostly been using the distro builds, which for neovim often meant an outdated version. I can also admit that I've benefited from the project, even if I've never used it. Like everyone using Firefox is currently benefiting from WebRender, despite never moving to Servo. We often find criticisms of forks in OSS (waste of resource, we should work together…

Agreeing with another response: I have a vimrc that I've accumulated over something like 20 years, I kept putting off switching to Neovim because I anticipated it would be a headache, and in the end it only required something like half an hour to make the switch, probably less. I would classify it as "easy peasy".

Re: Neovim v0.4.0

#153

Post by PeCaN »

justinmk wrote: post #32
maccam94 wrote: post #25

Earlier quoted context omitted.

Yes, neovim is compositing the windows inside the text UI in a terminal.

Replying to PeCaN: > slightly concerned that neovim started to cut bloat in vim and ended up implementing a compositing window manager with fake transparency. "Window manager" existed since vim got split-windows (1990s). Redesigning it as a compositor: - isolates windows logically, so that UIs can do their own layout instead of being stuck with the TUI grid - useful for implementing floating windows - allows reasonin…

This is reasonable enough, but personally I'm not really convinced a text editor should be handling windows at all, especially since neovim allegedly is designed to be embedded by a ‘real’ UI (and presumably could be embedded by a terminal-based UI that handles windows—or just uses tmux).

I do recognize that I prefer software to be simpler than most people (for the record, much of the time I use ed(1)).

Re: Neovim v0.4.0

#154

Post by soraminazuki »

m712 wrote: post #96
alpaca128 wrote: post #83

Earlier quoted context omitted.

Because Vim modes usually don't support more than a handful of basic features, let alone plugins and custom keybindings. Vim also starts up without any noticable delay and can be used for every text file, no matter in what context.

>Vim also starts up without any noticable delay Only if you run it without any plugins. Unfortunately if you have a lot of third party packages, vim startup times start to get closer to emacs startup times (both of which are still better than any IDE I have used, of course). I keep a vim.norc alias in my alias file which launches vim with an empty .vimrc for this very reason.

I've found that profiling startup time and lazy loading plugins could reduce your startup time to 100~200ms even if you have more than 50 plugins.

Re: Neovim v0.4.0

#155

Post by wyclif »

the_duke wrote: post #39
mths wrote: post #35

Earlier quoted context omitted.

> Otherwise it is pretty much a drop-in replacement without issues. Except for the crashes. The crashes are an issue. Don't get me wrong though, I like nvim. I use it occasionally. But the crashes are an issue.

After using nvim for several years, I've never seen it crash once.

Same here. I use it constantly with a handful of plugins, never had an issue.

Re: Neovim v0.4.0

#156

Post by stompl »

maccam94 wrote: post #45
vhakulinen wrote: post #5

I'll just leave a shameless plug for my neovim GUI project here: https://github.com/vhakulinen/gnvim . It has a WIP PR[1] for implementing multigrid support, which would allow features such as scrollbars. There are many other GUIs too, such as oni/oni2, gonvim, neovim-gtk and neovim-qt. Extensive list can be found here: https://github.com/neovim/neovim/wiki/Related-projects#gui 1: https://github.com/vhakulinen/gnvim/…

> shameless plug You didn't even mention it's written in Rust!

Rust rust rust! stuffs mouths with cheerios, shouting while chewing Rust!

Arghhhhh

R U S T

U

S

T

Re: Neovim v0.4.0

#157

Post by fortran77 »

maccam94 wrote: post #45
vhakulinen wrote: post #5

I'll just leave a shameless plug for my neovim GUI project here: https://github.com/vhakulinen/gnvim . It has a WIP PR[1] for implementing multigrid support, which would allow features such as scrollbars. There are many other GUIs too, such as oni/oni2, gonvim, neovim-gtk and neovim-qt. Extensive list can be found here: https://github.com/neovim/neovim/wiki/Related-projects#gui 1: https://github.com/vhakulinen/gnvim/…

> shameless plug You didn't even mention it's written in Rust!

The first rule of the Rust club is: "Always talk about the Rust club"

Re: Neovim v0.4.0

#159

Post by alpaca128 »

m712 wrote: post #96
alpaca128 wrote: post #83

Earlier quoted context omitted.

Because Vim modes usually don't support more than a handful of basic features, let alone plugins and custom keybindings. Vim also starts up without any noticable delay and can be used for every text file, no matter in what context.

>Vim also starts up without any noticable delay Only if you run it without any plugins. Unfortunately if you have a lot of third party packages, vim startup times start to get closer to emacs startup times (both of which are still better than any IDE I have used, of course). I keep a vim.norc alias in my alias file which launches vim with an empty .vimrc for this very reason.

Strange. I use 15 plugins and according to the --startuptime flag NeoVim takes 32ms to start. Vim takes about twice as long, but that's still so incredibly fast I'd call it instant. I guess when it comes to plugins there are some real heavy-hitters out there that I somehow managed to never try.

Re: Neovim v0.4.0

#160

Post by iamnotacrook »

NilsIRL wrote: post #132
Aissen wrote: post #43

I want to take a moment to thank the Neovim authors, as a VIM user. Thanks to you, VIM has felt the pressure and greatly improved, including the vim 8 async plugin feature (which has now trickled-down in all distros). I can now use coc.nvim and ccls to have an IDE-like experience inside vim, which really helps reducing further the write-compile-test-fix loop.

Why are you still using VIM if you like Neovim's features? (this is not a rhetorical question)

Speaking for myself; vim's always available whereas I have to faff about (especially on older systems, or where I'm not admin) to get neovim working. The .vimrc files seem to have to live in different places meaning the scripts I've written to install vim/vim-plugins will need to be altered. Some plugins don't work properly. I've never got neovim working on windows (can't get the colours quite right) I tried the built-in terminal and thought it was a great idea but struggled to seamlessly hop between panes, pipe the output into files and open in other windows or copy/paste them. Tmux solves all those problems so I never use the terminal (and if I needed to it's in vim now).

I liked the attitude of the project, but I still have no use for it. One idea which might make sense would be for the vim project to accept the neovim source; merge it back in as vim 9 so all the great refactoring, and other functionality is available for everyone and any wasted effort on two almost-identical projects is avoided.

Post reply on HN