Comment.nvim VS awesome-neovim

Treesitter is a syntax parser that'll build a tree-like structure to enable anything from excellent syntax highlighting through to complex refactoring. There are so many creative ways you can use Treesitter, from jumping around text objects to commenting sections of code, it's a must-have in my books.

A couple nice quality of life plugins would be: Comment (which lets you use a keybinding to comment/uncomment things), Autopairs (which will make the paired brackets/parentheses/etc.), and Rainbow2 (which color-matches the pairs if things like parentheses).

I am reading the documentation for the [Comments](https://github.com/numToStr/Comment.nvim] plugin with :h comment.config and I see this

I was wondering what plugins you use for comments, actually, I'm using numToStr/Comment.

Nowadays, people (mostly) autogenerate their help docs with either markdown or emmmylua are their source. You are facing an issue that I faced before with Comment.nvim.

Comment.nvim?

Based on your reply I recommend taking out the comment plugin, replacing it with https://github.com/nvim-treesitter/nvim-treesitter-textobjects and https://github.com/numToStr/Comment.nvim

Hay mas recursos en: Neovim's Awesome List.

Make sure to checkout Neovim's Awesome List for more.

I personally don't use this functionality so I can't recommend a specific plugin, but if you search for “treesitter”/“tree-sitter” in this list, you will find several of them:

https://github.com/rockerBOO/awesome-neovim

Does the community have a central repository of all plugins? I’ve used both this repo and neovim craft. If the latter creator has exposed the data via api that’s a fantastic plugin idea.

I like the poster you made, and I think this can definitely help people who first creating their config :) Did you submit it to the big-list yet?

> I'm using vim for a long time now, but recently I heard that neovim is noticeably faster. Is that true?

Yes; of course, YMMV. Even if you use Neovim just like Vim, it's snappier—the refactor resulted in 30% less code.

> Have most folks switched to neovim by now? Should I care?

There's two broad groups. Users who have been using Vim for like 20 years and they have a configuration they like and see no reason to change.

The other group wants all of the new hotness of Language Server Protocol, tree sitter, everything's asynchronous, there's a proper API and lots of new plugins that wouldn't be possible using Vimscript, for the most part.

Check out https://neovim.io/doc/user/vim_diff.html#nvim-features for details.

Being a Vim (now Neovim) user for close to 20 years, Neovim has attracted lots of new people to Vim-style editors and they've brought lots of energy. There's also been quite an influx of VS Code users.

Neovim is not an IDE, but it can support many IDE-like features via plugins written in Lua. There are several Neovim distributions, which you can install quickly and play around without committing to anything [1]. LunaVim, LazyVim and AstroVim are popular Neovim distributions.

It's important to understand that your existing .vimrc will Just Work if you want to start with that.

[1]: https://github.com/rockerBOO/awesome-neovim#preconfigured-co...

You can get some inspiration in the Awesome Neovim repo. Also, check lazy.nvim's README to see how to actually add and manage your plug-ins.

Collection of Awesome Plugins: https://github.com/rockerBOO/awesome-neovim

I started here: Awesome Neovim, it has a huge list of nice things to use for your own setup. I watched a few tutorials on youtube to know with which plugins to start.