vim-gutentags VS cmake4vim

https://github.com/ludovicchabant/vim-gutentags/issues/139 has some background.

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.

The plugin is here and adds features like kits, customizable build types, support for running ctest, automatic updates/restarts of clangd LSP server and also provides some functions that allow cool plugin customization. Basically, you get features that are mostly equivalent with features from the plugin I used in vim, but implemented in Lua. Feel free to test it out. Note that I only tested it on my machine (M1Pro mac) and in one Linux container, so expect bugs, crashes and various errors. Feel free to post issues and PRs with fixes.

The plugin depends on cmake4vim (a plugin for CMake integration with Vim/Neovim), this allowed to have deeper integration of gtest-vim for CMake projects (you can just switch between CMake targets in order to run different tests).

Around the year ago, I have posted the last post about cmake4vim plugin updates.

CMake integration: https://github.com/ilyachur/cmake4vim

Not sure if you want to add a other plugin, but I've had good results with cmake4vim. It integrates with Dispatch if it's installed.

Good question! And for Cmake projects I really like the cmake4vim plugin from ilyachur. https://github.com/ilyachur/cmake4vim

I think, that you can do such 'advanced' features without used plugins. Concerning my C++ workflow, I'm using it with Cmake and https://github.com/ilyachur/cmake4vim plugin adds the possibility to compile it in a few commands. Also, I've added a feature to run the CMake target with the use of one command and hope, that soon it will be merged.

Here is the issue with the video https://github.com/ilyachur/cmake4vim/issues/68