hibiscus.nvim VS vim-gutentags

local function bootstrap(url, ref) local name = url:gsub(".*/", "") local path = vim.fn.stdpath [[data]] .. "/lazy/" .. name if vim.fn.isdirectory(path) == 0 then print(name .. ": installing in data dir...") vim.fn.system { "git", "clone", url, path } if ref then vim.fn.system { "git", "-C", path, "checkout", ref } end vim.cmd [[redraw]] print(name .. ": finished installing") end vim.opt.runtimepath:prepend(path) end bootstrap("https://github.com/udayvir-singh/tangerine.nvim") -- Optional and only needed if you also want the macros bootstrap("https://github.com/udayvir-singh/hibiscus.nvim") require 'tangerine'.setup { target = vim.fn.stdpath [[data]] .. "/tangerine", -- compile files in &rtp rtpdirs = { "ftplugin", }, compiler = { -- disable popup showing compiled files verbose = false, -- compile every time changes are made to fennel files or on entering vim hooks = { "onsave", "oninit" } }, }

I can recommend using Fennel with Tangerine (integration) and Hibiscus (macros). My config here for inspiration.

For ease of use, you can use conjure for evaluating the code, cmp-conjure for nvim completions, hibiscus.nvim and nyoom.nvim macros for macros, and you can also use nyoom.nvim as a base config.

Hibiscus.nvim:

local function bootstrap (name, url, path) if vim.fn.isdirectory(path) == 0 then print(name .. ": installing in data dir...") vim.fn.system {"git", "clone", "--depth", "1", url, path} vim.cmd [[redraw]] print(name .. ": finished installing") end end bootstrap ( "tangerine.nvim", "https://github.com/udayvir-singh/tangerine.nvim", vim.fn.stdpath "data" .. "/site/pack/packer/start/tangerine.nvim" ) bootstrap ( "hibiscus.nvim", "https://github.com/udayvir-singh/hibiscus.nvim", vim.fn.stdpath "data" .. "/site/pack/packer/start/hibiscus.nvim" ) require'tangerine'.setup{ compiler = { verbose = false, hooks = { "onsave", "oninit" } } }

Fennel with hibiscus:

But, you can use another plugin of mine Hibiscus which contains bulk of zest and aniseed macros.

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.