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

121–130 of 220 posts

Re: Neovim 0.7 Released

#121

Post by wyclif »

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?

Re: Neovim 0.7 Released

#122

Post by mypalmike »

lambdaba wrote: post #45
snowram wrote: post #19

Earlier quoted context omitted.

Same reaction but in the opposite direction. I still do not understand why some people are that obsessed to dedicate a large amount of time learning a software that will sometimes make their life a tiny bit easier in rare edge cases. Every time I try to learn how to use Vim as an IDE, I just end up massively overwhelmed and never even come close to reach a fraction of my productivity on VSCode. The fact I cannot see…

Most people I know that use Vscode now are coming from TextMate -> Sublime Text -> Atom -> VScode. Meanwhile my Vim go brrrrrr :D Seriously, there's a huge benefit to not constantly switching and learning new environments (admittedly since Neovim / switching to Lua for scripting Vim there's been a lot new but all things the community wanted)

Seriously, there's no benefit to sticking with one environment. The right tool for the job. If you're doing Java for instance, no version of vim or emacs comes close to the functionality of the popular IDEs. With vi perhaps you can type more efficiently. With a good IDE, you can develop far more efficiently. For modifying bash scripts on remote machines, vim all the way.

Re: Neovim 0.7 Released

#123

Post by qbasic_forever »

andrewmcwatters wrote: post #99

Neovim is such a weird derivative utility to me. Derivative/forked software usually isn't very successful to begin with, but then Neovim makes attempts to be modern and it's so not appealing at all. Here are some 5 second examples. Example 1: nvim . Still uses Netrw, which is fine, but doesn't even attempt to do things like: let g:netrw_preview=1 let g:netrw_banner=0 let g:netrw_browse_split=4 let g:netrw_liststyle=…

I don't want line numbers, IMHO it's an anti-pattern to have them. I'm not writing code trying to maximize the number of lines, or show my boss "look I wrote 10k lines today, so productive!". I'm trying to write less lines of code--if a function is sprawling past a page then I'm getting suspicious that it's too complex.

If I have to remember "ok line 7000 is where the weird permission business logic starts" that's a failure to comment and make clear how the code is structured.

If tooling is telling me there's a problem on a specific line then I should have a code action or command to take me directly to that line, I shouldn't have to juggle navigation manually.

Re: Neovim 0.7 Released

#124

Post by mjlbach »

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…

> Cause we can siphon from the huge man-hours of development and polish that M$ has put on VSCode.

Anything done on the language server side is already coc/built-in client agnostic (since communication is done over json-rpc, except for tsserver which MS has not yet exposed via the LSP, so we rely on the typescript-language-server-wrapper), anything on the client side is marginally useful at best.

Re: Neovim 0.7 Released

#125

Post by wyclif »

davidkunz wrote: post #82
annowiki wrote: post #55

Earlier quoted context omitted.

The debugger. I made your same argument for years to a buddy of mine that always used WebStorm (I'm a Python dev and he kept pushing me to try PyCharm). A coworker pushed me to try PyCharm since we're on Windows and I haven't really looked back. I even bought CLion. If you can point me to an easy debugger to set up in neovim I'd probably be right back, but I can't. Couldn't figure out how to set up vimspector. And in…

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 knew I'd watched the first two videos at some point because when I opened this page, those first two links were the only ones greyed out. Good stuff.

Re: Neovim 0.7 Released

#126

Post by ksala_ »

Winsaucerer wrote: post #112
sophacles wrote: post #21

Earlier quoted context omitted.

Both vim and neovim have the ability to open a terminal in a window split. It's not my preferred workflow but some people really like it rather than tmux or ctel-z to drop onto a shell... the implementation of this feature in neovim is a lot nicer than the one in vim. One thing i do use it for: In neovim there's options to open the terminal as a sort of overlay on top of the existing splits, they call it floating ter…

It's really useful to be able to use visual mode on your terminal window, to copy things. That's something you don't get via ctrl-z or tmux.

Tmux has support visual mode (at least character and line), I use it all the times.

I don't remember if it's enabled by default, but I have this in my ~/.tmuxrc (where pbcopy is the excellent https://github.com/skaji/remote-pbcopy-iterm2/blob/master/pb...)

  # Enable vi mode
  setw -g mode-keys vi

  # Copy to host
  bind-key -T copy-mode-vi v send-keys -X begin-selection
  bind-key -T copy-mode-vi y send-keys -X copy-pipe "pbcopy"
  unbind -T copy-mode-vi Enter
  bind-key -T copy-mode-vi Enter send-keys -X copy-pipe "pbcopy"
It mostly work as expected, ctrl+B ] enter copy mode, then you can use / and ? to search, v to enter character visual mode, V to enter line visual mode and y/enter to copy the selection.

Re: Neovim 0.7 Released

#127

Post by mjlbach »

qbasic_forever wrote: post #114
canaus wrote: post #101

Earlier quoted context omitted.

I came from coc.nvim and switched to the native LSP when it was released on nightly. For a while I was using VSCode and came back to nvim and switched back to coc.nvim. I found that the native LSP's community to be too quickly changing. Plugins that were necessary earlier weren't, while new necessary plugins came into play. But, coc.nvim was steady chugging along and my old settings file worked out of the box. I'm al…

Yeah autocompletions are a mess with native LSP. In the last 6 months or so there have been ~3 different plugins around to support autocompletion, and each one fell into unmaintained or unused status. I hope eventually there is a stable, native solution for it.

nvim-cmp has been the dominant plugin for about a year now, and I keep the lspconfig wiki (mostly) up to date +/- a few days if anything changes

Re: Neovim 0.7 Released

#128

Post by jethro_tell »

heydonovan wrote: post #62
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 al…

That's a brew packaging problem. Haven't used it for years but it happened enough for me that I just went to Linux where packaging wasn't an issue.

Re: Neovim 0.7 Released

#130

Post by iamdbtoo »

bachmeier wrote: post #97

One of the appealing things about Neovim has always been > MessagePack structured communication enables extensions in any language Is anyone writing extensions in other languages? Does it work well?

I don't know how well or not it works, but there is an autocomplete plugin being written in Rust.

https://github.com/noib3/nvim-compleet

Post reply on HN