Live data from Hacker News

Neovim 0.8 Released

github.com

131–140 of 230 posts

Re: Neovim 0.8 Released

#131
post #84

If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ , or new native GUI editors like https://zed.dev/ ? It's impressive to see what the Neovim community has built — preconfigured setups like https://nvchad.com/ are especially wild. But it still feels like a huge amount of work, hoop jumping, and _fragility_ just to reach parity with V…

I really like working inside a terminal, and I like being able to navigate seemlessly between code tabs and terminal tabs as though they are one. I can do this easily in vim+tmux, I can't do this easily in IDEs where the mouse is considered first-class. I do miss certain features of IDEs, but being able to toggle between shells, tabs and code is my killer feature.

I just switched to this setup now... Before, I was using kate (which is very nice) but I switched exactly for the reason you've mentioned. terminal and editor in the same place.

Re: Neovim 0.8 Released

#132

Neovim is one of those things that seem maybe cool, but I just can't find a reason to switch. Vim works just fine for me, I don't know what I would be getting by switching, and I'd probably waste some time porting my config and workflow to whatever the differences are (I'm a heavy user of :terminal).

Vim user for 15+ years here. Switched to neovim last December to try out Github's Copilot plugin (which only supported neovim), and it was basically a drop-in replacement for vim. And I haven't looked back.

I'm also a heavy user of terminal though, and that was the one thing I spent extra time on, because there were subtle differences that I didn't like. If you give neovim a shot again, try this in your ~/.config/nvim/init.vim (aside: I do miss the simpler path of ~/.vimrc):

  " Neovim's default terminal mode bindings aren't great.                                                                  
  " This makes them behave like vim's.
  tnoremap  
  tnoremap  

  "Always enter the terminal in insert mode
  autocmd BufWinEnter,WinEnter,BufEnter term://* startinsert
  autocmd TermOpen,TermEnter * startinsert
  command! -nargs=0 Terminal :vsplit | term
This allows navigating across splits more seamlessly, and I like defaulting to insert mode whenever I move into a terminal. I also added the :Terminal command because I prefer them in a vsplit by default.

Re: Neovim 0.8 Released

#133

If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ , or new native GUI editors like https://zed.dev/ ? It's impressive to see what the Neovim community has built — preconfigured setups like https://nvchad.com/ are especially wild. But it still feels like a huge amount of work, hoop jumping, and _fragility_ just to reach parity with V…

https://v2.onivim.io

I was always bummed OniVim v2 didn't take off.

It was a native IDE but fully supported VS Code plugin system.

Re: Neovim 0.8 Released

#134

Earlier quoted context omitted.

I enjoy a terminal workflow, and helix doesn't actually have vim key bindings and many years of vim use is hard to switch. EDIT: I'm also a tmux user and I can't live without a replacement for this plugin: https://github.com/christoomey/vim-tmux-navigator

Check wezterm, it has something similar to tmux splits and it's nice.

Kitty also has this feature built in!

Re: Neovim 0.8 Released

#135
post #106

Earlier quoted context omitted.

> VS Code is a proprietary, spyware-riddled, resource-wasting worked example of why "modern" software sucks. Perspectives like these (and others in the thread) remind me that there exists a separate cohort of engineers from people like myself which have absolutely polar opposite views. I respect your opinions, though I couldn't disagree more with them! :) Well, except the bit about VSCode having "spyware". That's not…

> and you should just call it that instead. And then turn it off using the built-in setting: https://code.visualstudio.com/docs/getstarted/telemetry#_dis...

   - https://www.roboleary.net/tools/2022/04/20/vscode-telemetry.html
      - "It looks like you cannot shut telemetry off 100%. These settings will
        opt you of most data sharing scenarios; but not all data sharing
        scenarios."
      - Apparently even VSCodium can't kill it all
         - https://github.com/VSCodium/vscodium/blob/master/DOCS.md#disable-telemetry

Re: Neovim 0.8 Released

#136

If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ , or new native GUI editors like https://zed.dev/ ? It's impressive to see what the Neovim community has built — preconfigured setups like https://nvchad.com/ are especially wild. But it still feels like a huge amount of work, hoop jumping, and _fragility_ just to reach parity with V…

Why? Here are some reasons in no particular order!

* +20 years of muscle memory

* Total customizability, when you get good at configuring and writing small scripts it feels like you can do anything. VSC feels like it's all about plugins

* On the fly remaps. E.g writing latex and quickly add insert mode remaps for things you are currently writing about ":imap CO2 $CO_{2}" for a prettier version of CO2 as you type. Playing around with Zig? With ":map ,t :w:!zig test %" you can type ,t and it saves and tests the current file.

* Write simple scheme files for pattern matching with Treesitter to conceal unnecessary clutter in some programming languages

* Snippets, other editors have this as well but with Luasnip I program every aspect of how it works exactly as I want it

* Even with a bunch of plugins it starts in less than 100ms

Re: Neovim 0.8 Released

#137

If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ , or new native GUI editors like https://zed.dev/ ? It's impressive to see what the Neovim community has built — preconfigured setups like https://nvchad.com/ are especially wild. But it still feels like a huge amount of work, hoop jumping, and _fragility_ just to reach parity with V…

What exactly is fragile about vim/neovim? I'd argue that they are incredibly stable, being as old as they are.

For another point I don't see being brought up, I love the .vimrc file. You can version control your entire editor config in one file. Other editors tend to spread config out across different files (one per plugin for example).

I've had to spend time configuring every editor I've used, but all that time is tracked and documented in vim. I can have everything set up instantly.

Re: Neovim 0.8 Released

#138
post #21

Neovim is one of those things that seem maybe cool, but I just can't find a reason to switch. Vim works just fine for me, I don't know what I would be getting by switching, and I'd probably waste some time porting my config and workflow to whatever the differences are (I'm a heavy user of :terminal).

I switched to neovim because of LSP (Language server protocol) support. I know there are libraries (or whatever cool kids call it these days), which brings this functionality to og vim, but the lsp integration in neovim just works so nicely out of the box.

Hold on, you don't need anything like Ale or CoC to run LSPs in neovim?

Re: Neovim 0.8 Released

#139

If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ , or new native GUI editors like https://zed.dev/ ? It's impressive to see what the Neovim community has built — preconfigured setups like https://nvchad.com/ are especially wild. But it still feels like a huge amount of work, hoop jumping, and _fragility_ just to reach parity with V…

vim, or at least vi, is something you can pretty much expect to be existing on any system you ssh into. If you are comfortable with vim, you have the editor part sorted no matter what system you are dropped into to debug/whatever.

Re: Neovim 0.8 Released

#140

A text editor without a well rounded GUI story isn't worth it for me. There are all these desperate projects each with their own focus, ranging from "simple graphics acceleration" to "tons of bells and whistles, animations and ad-hoc UI extensions". UI should be thought out at PRs and issues, but the same people who develop the main core. But they don't have to, because they're making a terminal application, which ha…

By vim user count alone, I would conjecture that the venn circle of philosophically opposed devs has more people insisting on the absence of a GUI story, than those insisting on one.

Of course the vast majority of devs use whatever suits them, GUI or not.

And you couldn't have picked an editor with a worse GUI story.

Post reply on HN