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

91–100 of 213 posts

Re: Neovim v0.5

#91

Post by pasabagi »

luke2m wrote: post #21

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

Well, a lot of people have come up with good reasons, but for me, it really comes down to the old repairman's adage: there are two kinds of people, those that piss in lifts, and those that do not.

Now, pretty much any programmer can read a lua program, and it takes about an hour to learn, whereas I think the most flattering honest word anybody has ever used to describe vimcsript as is 'pathological'.

For the second kind of person, vimscript is like some combination between russian roulette and vogon poetry, bomb defusal and surreal nightmare. For the first kind of people - I don't know, there are probably some upsides, but honestly, who does that? Do you? That's what you have to ask yourself.

And more, if you're not that kind of person today, do you want to become that person?

Re: Neovim v0.5

#92

Post by prince781 »

gen220 wrote: post #76
prince781 wrote: post #52

Earlier quoted context omitted.

> 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! :)

Ah, I misread your comment. My apologies.

Yeah, perhaps this does make neovim more a monolith, as there are already great plugins like coc.nvim that can be used. However, I believe the expectations of a modern text editor have been raised sufficiently in the last few years that we now expect to have code intelligence baked in, just like we came to expect baked-in syntax highlighting decades ago over editors that lacked it back then.

Re: Neovim v0.5

#93

Post by maddyboo »

linsomniac wrote: post #89
maddyboo wrote: post #24

Earlier quoted context omitted.

Wow, I’ve been a vim user for like 8+ years and didn’t know about 0p even though I run into that problem all the time. I had even re-bound yank/paste to use a different register. Thanks for the pointer! This is what I love about vim, there’s always something new to learn.

LunarVim has a "show b̶u̶f̶f̶e̶r̶s̶ registers" plugin enabled so when you type " it brings up a window showing the contents of various buffers, so you can eyeball it rather than remembering.

Oh, just realized I misread the original comment. I ignored the “, so I thought they were saying you could just use 0p (on my phone, otherwise would’ve tested it in vim).

I use registers often but I admit I haven’t memorized the meaning of the auto-populated ones like 0.

Re: Neovim v0.5

#94

Post by nerdponx »

ssklash wrote: post #45

What is the value proposition for moving from vanilla vim to neovim? I see all the features on the neovim repo, but almost all of them seem aimed at developers rather than users. I've considered switching, but I'd have to move to a .nvimrc or something, update my install scripts and Ansible, etc., and I'm not sure what I'd gain from it other than "extensibility". If there are concrete benefits for normal usage, I'd b…

I initially switched because it allowed me to simplify my configuration. This was even before Lua integration was a thing; it had better defaults, and the client/server architecture appealed to me. I also liked the idea of a re-factored, more-modular, possibly faster core application.

Now what's starting to happen is that the plugin ecosystems are diverging. Subjectively, it seems like plugin developers are significantly more productive working in languages that are not Vimscript. Accordingly, Neovim seems to be accumulating more sophisticated IDE-like plugins, and this appeals to me on a personal level.

Now that the remote plugin and Lua APIs (including Tree Sitter and LSP!) are somewhat stable, I expect this productivity and divergence to accelerate. I feel like Neovim will be approaching Emacs "power parity" in the next few years, and that's a very exciting prospect to me.

Re: Neovim v0.5

#95

Post by leephillips »

linsomniac wrote: post #89
maddyboo wrote: post #24

Earlier quoted context omitted.

Wow, I’ve been a vim user for like 8+ years and didn’t know about 0p even though I run into that problem all the time. I had even re-bound yank/paste to use a different register. Thanks for the pointer! This is what I love about vim, there’s always something new to learn.

LunarVim has a "show b̶u̶f̶f̶e̶r̶s̶ registers" plugin enabled so when you type " it brings up a window showing the contents of various buffers, so you can eyeball it rather than remembering.

I guess you mean registers. You can see a list of them in default Vim using the command :reg.

Re: Neovim v0.5

#96

Post by nerdponx »

_benj wrote: post #62
soupshield wrote: post #59

My heart is with vim but I switched to emacs as I love orgmode too much for note taking. I tried a few vim orgmode plugins but they seemed quite flakey even though I only really use orgmode for outlining. Excuse my ignorance but could all this LSP/Lua stuff allow neovim to take over from emacs?

I’d say cautiously maybe. Using lua to me seems like it could open doors for neovim that before we’re either not possible or very complicated to do with vimscript. Neovim doesn’t have such incredible and almost ridiculous power to change itself like emacs does with elisp since vim is still not written in lua, lua is just used to access its api, but that api is quite extensive. So, maybe? Hopefully?

And if you really want Lisp in Neovim, you can use the Aniseed framework to write your plugins and scripts in Fennel.

Re: Neovim v0.5

#97

Post by thayne »

efficax wrote: post #78
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

I tried switching to VSCode with the vim plugin. but I got frustrated with vim keys that didn't quite work right on VSCode. And iirc configuring custom vim-style bindings was quite a pain. And then there were the neovim/vim plugins that I used that didn't have good equivalents in VSCode, especially that worked well with the vim plugin.

Also VSCode is much, much more resource hungry.

Re: Neovim v0.5

#98

Post by davidkunz »

systems wrote: post #87
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 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.

Re: Neovim v0.5

#99

Post by davidkunz »

mraza007 wrote: post #55
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...

Thank you for making these !!!

Glad you like them!

Re: Neovim v0.5

#100

Post by shiryel »

systems wrote: post #87
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 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...
Post reply on HN