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

151–160 of 220 posts

Re: Neovim 0.7 Released

#151

Post by xigoi »

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…

On the other hand, in IDE requires commitment to using only a few select programming languages.

Re: Neovim 0.7 Released

#152

Post by xigoi »

wyclif wrote: post #121
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…

Just curious: you mentioned SSH. What is currently the optimal way to setup vim/neovim over SSH and carry all your configuration over with you to different servers?

Just use your favorite version control system?

Re: Neovim 0.7 Released

#153

Post by JodieBenitez »

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…

> I really don't understand the comments of "I will literally not spend a single minute configuring my editor".

It's really not difficult at all. I and others have probably a million things we would like to tinker with (yes, including tweaking a text editor), but we all have a limited time so we end up with priorities. It just happen that I didn't make a priority to tweak vim/neovim because I'm happy with my current code editing setup. For other kinds of software, I may not be happy at all, to the point of writing my own.

See: different people, different expectations. Your choice being right for you doesn't mean it's the right choice for everyone. Tolerance 101.

Re: Neovim 0.7 Released

#154

Post by davidkunz »

wussboy wrote: post #106
davidkunz wrote: post #82

Earlier quoted context omitted.

Debugging in Neovim is quite simple, I recommend nvim-dap, I made a few videos: https://youtu.be/ga3Cas7vNCk https://youtu.be/SIYt1dopfTc If you prefer Vimspector: https://youtu.be/-AZUIL1rY3U

I watched your first video. As someone who likes the idea of Vim and has learned many of the keyboard shortcuts, my impression of the video was "Debugging in Neovim is quite simple. Just remember these 35 keyboard shortcuts."

That's true, it requires a bit of memorization and configuration. I've put the shortcuts similar to character movements: CMD + j,k,l (jump over, jump out, jump in).

Re: Neovim 0.7 Released

#155

Post by pdimitar »

lawn wrote: post #102
pdimitar wrote: post #41

Earlier quoted context omitted.

I absolutely want to learn VIM but saying it's only a weekend is plain misinformation. We're definitely looking at months of gradually building new habits.

I think the difference between your and the other opinion is what does "learn vim" mean? Is it enough to know how to enter insert mode, make an edit, then save and quit? That's easy enough to learn in a weekend. Or is it learn how to edit efficiently using the various vim commands? That will indeed take much longer than a weekend. (Even getting it configured just the way you want to will probably take more than a wee…

You're correct. I learned enough VIM to use it as my Git commit message editor. Beyond that... it's a journey as you said.

Re: Neovim 0.7 Released

#156

Post by mjlbach »

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

I think currently Helix targets a different audience. Helix does not have a plugin system (there is an ~1 year old proposal to use WASM but until it is functional the point is moot) or embedded scripting language, so your ability to customize it is extremely limited.

Re: Neovim 0.7 Released

#157

Post by capableweb »

ufo wrote: post #115
bbkane wrote: post #91

Earlier quoted context omitted.

Do the kakoune and neovim keyboard shortcuts conflict for you? I've put off trying non-vim modal editors because I think there's only enough room for one set of shortcuts in my head. How difficult is it for you to switch between them?

It's not too bad, because the most basic commands are about the same. The ones that get me the most are dd and V. When I switch to the other editor I get these wrong a couple of times before the mental model readjusts. That said, I never was a super advanced vim user because I couldn't remember the rarely used motions. Part of the reason I started using kakoune is that I find it easier on my brain. Basically everythi…

I've been using vim (neovim) for more years than I can count, but there is still so many movements that doesn't stick in my head, probably because I don't use them so much.

I recently came across the which-key.nvim (https://github.com/folke/which-key.nvim) neovim plugin, which helped me a lot to speed up finding what movement I want to do. It basically shows you a popup with what combinations are possible after you press any key (while nvim waits for the next one), so you can basically explore commands by just pressing keys, instead of having to look them up.

Re: Neovim 0.7 Released

#158

Post by mjlbach »

mikewhy wrote: post #141
elpatoisthebest wrote: post #84

Earlier quoted context omitted.

I do recommend that new users just use coc.nvim, but not exactly because of what you said. Both coc.nvim and the built in LSP implementation use basically the same Language Servers, so whatever updates happen to the server will benefit either approach. However, coc.nvim DOES have a large community that has built a neatly packaged LSP client framework (and many other tie-ins like completion, snippets, formatting, and…

> and many other tie-ins like completion, snippets, formatting, and things like auto-pairs This is usually where I check out when I get the urge to redo my vim setup. The fact that completion, auto pairs, snippets, and something like endwise are all at odds with each other isn't something I want to deal with.

> completion, snippets

This is fine in the nvim-cmp world, there's a config example in the lspconfig wiki, it's about 5 lines for the integration. The recommended lspconfig configuration (included snippets and autocompletion) has less lines of code than the example in the readme for coc.

> formatting

This is built-in to neovim's LS client (vim.lsp.buf.formatting()), adding an external formatter can be done with formatexpr (built-in)

Re: Neovim 0.7 Released

#159

Post by mjlbach »

lc9er wrote: post #79
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 agree with your coc.nvim assessment. It’s more cohesive and works pretty much out of the box. You have to assemble more plugins to recreate the functionality coc provides as a whole and the documentation on the config process is sparse (as of my last attempt to use it). I’m also probably a weird edge case in that my primary use case is writing Powershell. Coc just works and getting native LSP configured and working…

If you're having a powershell issue, you can file an issue. I'm not a Windows user or powershell user, but when I tested the PR (before merging it) I was able to get it running in a minute.

Re: Neovim 0.7 Released

#160

Post by ComputerGuru »

scottlamb wrote: post #138
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/

> One use case for the new remote functionality is the ability to open files from the embedded terminal emulator in the primary Neovim instance, rather than creating an embedded Neovim instance running inside Neovim itself. Hmm, if I type "git commit" within the terminal, is there some value of $EDITOR that would make it launch a buffer to edit the commit message, then finish when I close the buffer? (and if so, are…

I'm not sure if I understand you, but with EDITOR=nvim it'll do just that. To "commit" w/ the message you have in editor, ZZ. To abort, use :cq
Post reply on HN