Live data from Hacker News

Neovim 0.5 is overpowering

crispgm.com

201–210 of 429 posts

Re: Neovim 0.5 is overpowering

#201

Earlier quoted context omitted.

When is it going to get released?

https://twitter.com/TeejDeVries/status/1396881477263036417 ;) (I hope you are in on the meme, otherwise I am sorry for posting our "inside joke" response)

Jokes (and especially inside jokes) don't really go over well here on HN.

Re: Neovim 0.5 is overpowering

#202
post #2

Neovim 0.5 is awesome. It has native LSP support, Lua configuration support that it feels like true revolution over past versions. But, getting into optimal setup in neovim/vim involves lot of configuration. Here is mine if you want to refer: https://github.com/varbhat/dotfiles/tree/main/dot_config/nvi...

It is awesome, but I have been running into bugs with it. Memory out of bounds errors, freezing when my project is misconfigured, it doesn't feel stable yet. Is that just me?

I think it may just be you. I’ve been using nightly builds for months now, and haven’t seen what you describe even once.

Re: Neovim 0.5 is overpowering

#203
I've been on neovim nightly for about 6 months now, coding in it full time. Can't recommend it enough!

Use all the plugins highlighted here except telescope, which I've been holding off on from fears of slowness, but maybe I'll take the plunge this weekend and test it on some of the larger repos I work in :)

Re: Neovim 0.5 is overpowering

#204

Earlier quoted context omitted.

Or, you could have hit qt, recorded your commands for the first change, and then replicated it for every other line with a simple @t, instead of redoing all the changes each time. You don't have to learn command. You simply need to know how to edit with VIM. And multi cursors only work for tabular data. The macro recordings can work for the entire document where you call a macro on a word/regex you searched for, for…

I did record it with qd...q and repeated it with @d @@

Visual select and normal@t (assuming you saved it in t) is a good way to do it once for every line.

Re: Neovim 0.5 is overpowering

#205

I'm using vim happy no plugins no config just edit files do I need neovim?

No. There's no real benefit in this case. For the most part, the main practical advantage of Neovim over Vim (from a user perspective) is that there are some plugins that are only supported by Neovim and there are some types of plugins that might work better on Neovim. So if you're not using plugins this won't affect you.

There are some ideological advantages of Neovim over Vim, too, but those are relatively minor; neither is evil software, and it can be argued that Vim has some ideological advantages over Neovim, too.

For a plugin dev or vim/neovim dev, there may be other practical advantages one way or the other.

Re: Neovim 0.5 is overpowering

#206

Earlier quoted context omitted.

Out of curiosity, does your's have any benefits over NERDCommenter?

I'm sure mine's strictly worse. It was written when I was working in an environment where it was easier to spend 10 hours on something than it was to get permission / access to download vim plugins from the internet.

Gov?

Re: Neovim 0.5 is overpowering

#207
post #139

The real killer feature of Neovim is Firenvim ( https://github.com/glacambre/firenvim ). I'm still waiting for somebody to do the same thing with GTK inputs and the shell (yeah, I know that bash and zsh support a vim mode, but it sucks).

control + x followed by control + e will drop you into $EDITOR from your shell - might do what you want

Re: Neovim 0.5 is overpowering

#208

Earlier quoted context omitted.

I can never remember what all those different maps do: ':map', ':map!', ':nmap', ':vmap', ':imap', ':cmap', ':smap', ':xmap', ':omap', ':lmap', etc. do. There are bunch of questions on StackOverflow about different mapping options so I wouldn't say it's intuitive at all.

The differences that actually matter are self explanatory: map is for all modes, imap for insert mode, nmap for normal mode and vmap for visual mode (& tmap for terminal mode in NeoVim). The rest can be safely ignored as far as I can tell. Little confession: I have no idea what e.g. the difference between "nmap" and "nnoremap" is. But after years of randomly mixing them in hundreds of bindings without a noticeable di…

You're right, for most simple use cases it doesn't matter. But I once spent an hour on a weird bug that turned out to just be some plugin applying a map that I didn't know about and that I didn't know about map expansion. So I might be biased, but I think a loose understanding is helpful.

The default behavior is to recursively expand and apply your mappings and "noremap" disables this recursion. For example if you do something like

  :map j k
  :map q j
  :noremap w j
q is expanded to k, but w is expanded to j
Post reply on HN