tree-sitter-jinja2 VS nvim-treesitter

Ah I see! I think it should be done the other way around, ie you should use a parser for jinja and inject SQL. Since the above is not valid SQL. There are some WIP jinja parsers (for example this or this) although I haven't tried them.

vim.opt.rtp:prepend(lazypath) require('lazy').setup({ { "nvim-neorg/neorg", build = ":Neorg sync-parsers", opts = { load = { ["core.defaults"] = {}, -- Loads default behaviour ["core.concealer"] = {}, -- Adds pretty icons to your documents ["core.dirman"] = { -- Manages Neorg workspaces config = { workspaces = { notes = "~/notes", }, defaultworkspace = "notes", }, }, }, }, dependencies = { { "nvim-lua/plenary.nvim", }, { -- YOU ALMOST CERTAINLY WANT A MORE ROBUST nvim-treesitter SETUP -- see https://github.com/nvim-treesitter/nvim-treesitter "nvim-treesitter/nvim-treesitter", opts = { auto_install = true, highlight = { enable = true, additional_vim_regex_highlighting = false, }, }, config = function(,opts) require('nvim-treesitter.configs').setup(opts) end }, { "folke/tokyonight.nvim", config=function(,) vim.cmd.colorscheme "tokyonight-storm" end,}, }, }, }) require 'plugins' ```

Install nvim-treesitter

To use it, just update to the latest version of nvim-treesitter, and don't forget to run `:TSUpdate` and have the comment parser installed.

If you are using Neovim, Tree-sitter does this very well for quite a number of languages, inc C and C++. https://github.com/nvim-treesitter/nvim-treesitter

Zero-depency, yes, this is not another extension of navic. It does not even depends on nvim-treesitter or nvim-lspconfig, nor do you need to register an 'on_attach' function. as long as treesitter parsers or language servers are intalled correctly, the winbar should start working out of the box

Are you using tree sitter? If so support for this was merged relatively recently https://github.com/nvim-treesitter/nvim-treesitter/pull/4798

All you need is just the LSP working (with linter, formatter and diagnostics) and telescope. Seriously, telescope is the GOAT, way faster than a file tree, you end up using the filetree only to move, create and delete files/folders but if it's just for that, you might as well use the terminal instead. For the LSP, it's not only autocompletion and hints at hover but formatting and diagnostics. I use lsp-zero + null-ls + trouble. I exposed all of the keybindings on those so I can at least open my own configs for guidance. Oh yeah, having treesitter is probably a must too, and it has no keybindings on its base form.

I'd start with nvim-treesitter, nvim-lspconfig, and use rust-tools.nvim as an accelerant. Any remaining advice I'd have is about Neovim but not about Rust. That advice would also be mostly questions of taste for this-or-that decisions.