vim-awesome VS vim-gutentags

Vim is infinitely customizable. While Vscode allows you to change the app’s color scheme, install plugins, and change a few app settings, Vim offers you complete control over the editor’s experience. You have thousands of plugins to choose from. You can completely remap any keybinding and create new shortcuts for tasks in your daily workflow. And giving you more power as a developer, you can completely reprogram or automate your Vim experience with the built-in Vimscript language or Lua for Neovim.

This is a pretty good website for browsing vim plugins: https://vimawesome.com

VimAwesome is a website with a curated list of vim plugins. You can search by category or type for something that fits your needs. I highly recommend browsing the list just to see what there is.

I recently moved to Mac/OSX from Linux and have struggled with my vim setup. I found some installations bundles that attempt to set everything up for me, so I used one of those, iirc it is this one: https://vimawesome.com/ . However, I have some issues with it. While coding, I often want to jump around code blocks and I do so by taking advantage of the '{}' characters (curly braces) used for code blocks in the languages I use (javascript and C++). In vi, the '%' character can be used to jump between the matching curly brace. However, in my current setup, this does not work. How can I find how to make the '%' feature work again?

That is probably a couple of hours worth of work getting the plugins set up. Then you're in the wild west looking for things that are interesting. I suggest you stay as minimal as you can as long as you can, but there is plenty to find.

Find the desireable plug-ins from VIM Awesome this is one of the best places to find vim and neovim plugins. For this tutorial we will add couple of plug-ins to make our neovim look good and work like an ide.

Unfortunately not maintained anymore, but it updates automatically so is still somewhat useful.

Are you aware of https://vimawesome.com/ Makes it pretty easy to find plugins.

Hi everyone. I'm looking to have a better setup for Rust in neovim. I do have rust-analyzer installed for useful lsp things but I was hoping to get tags working for it as well. I was using vim-gutentags (https://github.com/ludovicchabant/vim-gutentags) for navigating useful functions and stuff but couldn't quite get it to work for rust. Is there a simple way to do it or do I need rusty-tags and some aucommand to get it to work?

use tags, I like https://github.com/ludovicchabant/vim-gutentags for this. I might use my local .vimrc to tweak the config (exclude compiled source files and other uninteresting things)

guttentag: https://github.com/ludovicchabant/vim-gutentags

Without more information, it's hard to point you in the right direction. The tags file could be out-of-date, in which case you can try to re-generate it (vim-gutentags for tags auto-generation). You could have 2 function declarations with the same name, in which case you can try :tag to cycle through tags (supports partials, like :tag F which will suggest FOO, FAR, FAB ...etc) or :tag to see a list of possible options (supports partials, like :tag F which will list FOO, FAR, FAB, ...etc) for various matching tags you can jump to (fzf.vim provides a tags fuzzy finder via :Tags). Maybe you're experiencing :h tag-priority?

ludovicchabant/vim-gutentags - Tags

You can then use :cnext and :cprev (or focusing the window and selecting an entry) to navigate between them.

As others have stated, you can also use ctags (plugins like https://github.com/ludovicchabant/vim-gutentags are useful for refreshing tags in a project), but for some languages you may need to add a tag definition (e.g. for something like rust or zig). For older languages like C you should be fine.

Not sure if it will help in this case, but I also depend on ctags for when the lsp fails (e.g. code it doesn't compile for some reason). Here you let a program create a tags file, e.g. I use https://github.com/universal-ctags/ctags (it seems it can parse json files, though I'm not sure what kind of tags are generated from this and if they will be useful to you) with https://github.com/ludovicchabant/vim-gutentags to update the tags file. The tags file just contains symbol names with locations where they are defined, and vim has builtin functionality to use these tags files :h tag and they (can) work filetype independent. For example if I mention a C type in a markdown document I can just use ctrl-[ to jump to its definition in the C source file. Possibly you can generate tags files yourself from the json files to help with this, the tags file format is not very complicated. Tags also are not very intelligent and depend on unique names for them to work well, there is the :h g_CTRL-] that can help, but for symbols that are very common (e.g. init or something that potentially has like 20+ definitions) it doesn't really work.