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

Neovim 0.7 Released

github.com

Post reply on HN
Print view View original

61–70 of 220 posts

Re: Neovim 0.7 Released

#61

Post by d0mine »

paskozdilar wrote: post #10
ilovecaching wrote: post #3

I will never understand why people choose VSCode/Jetbrains over a terminal based editor. I can edit the kernel with clangd and get hover reference, autocomplete, go to def, ref, dec, smart refactor, and that's on top of being able to easily jump and fix lint/bugs using Vim's already great support for parsing compiler errors. With term added (which is a core Vim feature) it also has excellent support for gdb debugging…

Vim/Neovim/Emacs/etc. require a certain "commitment" to them - you have to learn keybindings, for example. Moreover, if you want any fancy IDE features you're addicted to, like hints, autocomplete, static analysis, refactoring, etc. you have to configure it yourself, which still isn't quite straightforward as selecting a plugin in VSCode (perhaps this is a good feature idea?). Most people just don't think it's worth…

There are preconfigured emacs distributions such as Doom Emacs https://github.com/hlissner/doom-emacs#doom-emacs

Re: Neovim 0.7 Released

#62

Post by heydonovan »

ilovecaching wrote: post #3

I will never understand why people choose VSCode/Jetbrains over a terminal based editor. I can edit the kernel with clangd and get hover reference, autocomplete, go to def, ref, dec, smart refactor, and that's on top of being able to easily jump and fix lint/bugs using Vim's already great support for parsing compiler errors. With term added (which is a core Vim feature) it also has excellent support for gdb debugging…

Could not disagree more. For entertainment purposes, I've installed neovim with `brew install neovim`. Opened a small project with `nvim ~/projects/whatever`, and am presented with a screen full of errors (https://imgur.com/D0ydDIG). Pressing enter brings me to a blank screen with even more errors. It then drops me into a vim document with some modal screens and now now I'll probably spend hours researching what all these mean, why this is happening, etc.

All those features you've listed aren't anywhere on the homepage, how does one even do that? I'm interested in learning more, but to think one can do this in a weekend just isn't true.

While I'm sure I could figure out all these kinks, its just software, it's the time sink that makes me pause. I don't see the value here, but I also don't know what all it can do compared to my current workflow with VSCode.

Re: Neovim 0.7 Released

#63

Post by petepete »

ducktective wrote: post #35

People who have tried both vim and nvim: - I have a theory that using `coc.nvim` is still the superior solution even compared to a native LSP. Why? Cause we can siphon from the huge man-hours of development and polish that M$ has put on VSCode. Every time they tweak VSCode, we at downstream, enjoy the benefits. Am I wrong in my assessment? - Vim's regexp-based syntax highlighting is annoying. So I think nvim+tree-sit…

I like both COC and CMP (native).

COC is way easier to set up and the default config is fine.

CMP is lighter and more configurable, and it works really nicely with luasnip (my snippet engine of choice).

Under the hood they both use the same LSPs, but COC pulls them down and sets them up for you.

Re: Neovim 0.7 Released

#64

Post by totetsu »

Does any one have any advice for running neo vim on a centos host without admin to install it. (Short of hunting down all the source packages for dependencies and compiling)

Re: Neovim 0.7 Released

#65

Post by ptaken »

totetsu wrote: post #64

Does any one have any advice for running neo vim on a centos host without admin to install it. (Short of hunting down all the source packages for dependencies and compiling)

Try the appimage, should bundle everything

Re: Neovim 0.7 Released

#66

Post by dantondwa »

totetsu wrote: post #64

Does any one have any advice for running neo vim on a centos host without admin to install it. (Short of hunting down all the source packages for dependencies and compiling)

You can download the appimage from the website or you can install it using flatpak. Then set up an alias for "neovim" pointing either to the appimage or to the flatpak command.

Re: Neovim 0.7 Released

#67

Post by CameronNemo »

lucky_cloud wrote: post #53
gpanders wrote: post #24

I did a brief write up on some of the biggest new features here: https://gpanders.com/blog/whats-new-in-neovim-0-7/

> Add let g:do_filetype_lua = 1 to your init.vim file Seems odd to not mention how to do this in init.lua

Yeah. These conversions are fairly straightforward, though:

    vim.g. =

Re: Neovim 0.7 Released

#68

Post by OtomotO »

pdimitar wrote: post #52
OtomotO wrote: post #50

Earlier quoted context omitted.

I wouldn't say so. The basics are very simple. You just get used to formulate a (weird) sentence of what you want to do in your head, abbreviate it and then learn (or configure) the buttons.

The problem here is the "just" word. To you it's "just" (as in a day or two), to me it's "I have to learn to think in a new way and that will take a while". Filter bubbles, dude. ;)

True, I love to learn and especially learn new ways to think.

Everything is just a just for me ^^

Re: Neovim 0.7 Released

#69

Post by pkulak »

OtomotO wrote: post #54

I think Helix does a lot right on the "initial configuration" front. It comes with LSP and treesitter configured out of the box. Neovim on the other hand is heavily customizable, but you also have to do this for awesome functionality

You can get nvim packaged up with goodies out of the box with something like Lunarvim.

Re: Neovim 0.7 Released

#70

Post by zorr »

ilovecaching wrote: post #17
blowski wrote: post #5

Earlier quoted context omitted.

> I will never understand why people choose VSCode/Jetbrains over a terminal based editor. I don't want to use my valuable time learning how to get vim working in some super-optimal way that's hypothetically going to improve my productivity by 1%. JetBrains consistently works well enough for me that I'm not going to bother switching. 90% of my life is spent thinking about how to solve the problem so the editor is not…

It's a weekend of learning for a tool that you use your entire life. Any computer scientist should realize the power of amortization.

I'm a dev that spends 90% of his computer time with a JB IDE open and I'll give you my perspective on it. It just works out of the box (or with a couple of 1-click install plugins) for practically all my use cases.

* I mostly write Kotlin/Java for backend, desktop and Android projects. JB has that covered: Gradle integration, refactoring, navigation, dependency updates, documentation viewer, visual git log/diff/merge/rebase/blame, visual Android layout editor, visual JavaFX/Swing layout editors, run configurations, step through debugger that shows current variable state on top of my source code, all the android resource/variant stuff, test runners, trigger tests from source code, tool windows for docker (compose) or other services and probably much more.

* I do C/C++ development on some projects in Clion which has most of the stuff from above but :s/Gradle/CMake/g.

* Aside from the above I also use my IntelliJ Ultimate for Python, Ruby, Golang, Rust, Markdown, Mermaid graphs, Kubernetes yamls and Terraform hcl files, Lua and probably some more. All with the excellent IdeaVIM plugin so I have my modal editing and ex commands.

I gladly pay $600/year for all this. If I have to spend one day (likely more) on configuring vim/nvim to even do a subset of what I mentioned, then JB is cheaper.

So, that is why I switched from years of Vim use (and a couple years of Emacs before that) to JB and I haven't looked back. I don't see why I should artificially limit myself to vim/terminal only when JB+IdeaVIM gets me the best of both combined.

Post reply on HN