Does anyone have an example config loading nvim-cmp with luasnips using mini.deps ?

[therealjasonkenney]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

mini.deps

Question

I was trying out mini.deps and I got most of everything working, but nvim-cmp just does not seem to function at all. Asking before I jump down the rabbit hole of figuring out what's wrong.

[krovuxdev]

@therealjasonkenney I'm not sure if you read about mini.deps. You need to use now or later to execute it. You might also need to configure your lspconfig properly.
I copied the code from the Nvim-cmp guide:

require("mini.deps").setup()
local add, now, later = MiniDeps.add, MiniDeps.now, MiniDeps.later
add({
	source = "neovim/nvim-lspconfig",
	depends = {
		"hrsh7th/cmp-buffer",
		"williamboman/mason.nvim",
	},
})
add({
	source = "hrsh7th/nvim-cmp",
	depends = {
		"hrsh7th/cmp-buffer",
		'hrsh7th/cmp-vsnip',
		'hrsh7th/vim-vsnip',
		"hrsh7th/cmp-path",
		"hrsh7th/cmp-nvim-lsp",
		"saadparwaiz1/cmp_luasnip",
		"L3MON4D3/LuaSnip",
	},
})
now(function()
	require("mason").setup()
	local cmp = require("cmp")

	cmp.setup({
		snippet = {
			-- REQUIRED - you must specify a snippet engine
			expand = function(args)
				vim.fn["vsnip#anonymous"](args.body) -- For `vsnip` users.
				-- require('luasnip').lsp_expand(args.body) -- For `luasnip` users.
				-- require('snippy').expand_snippet(args.body) -- For `snippy` users.
				-- vim.fn["UltiSnips#Anon"](args.body) -- For `ultisnips` users.
				-- vim.snippet.expand(args.body) -- For native neovim snippets (Neovim v0.10+)
			end,
		},
		window = {
			-- completion = cmp.config.window.bordered(),
			-- documentation = cmp.config.window.bordered(),
		},
		mapping = cmp.mapping.preset.insert({
			["<C-b>"] = cmp.mapping.scroll_docs(-4),
			["<C-f>"] = cmp.mapping.scroll_docs(4),
			["<C-Space>"] = cmp.mapping.complete(),
			["<C-e>"] = cmp.mapping.abort(),
			["<CR>"] = cmp.mapping.confirm({ select = true }), -- Accept currently selected item. Set `select` to `false` to only confirm explicitly selected items.
		}),
		sources = cmp.config.sources({
			{ name = "nvim_lsp" },
			{ name = "vsnip" }, -- For vsnip users.
			-- { name = 'luasnip' }, -- For luasnip users.
			-- { name = 'ultisnips' }, -- For ultisnips users.
			-- { name = 'snippy' }, -- For snippy users.
		}, {
			{ name = "buffer" },
		}),
	})

	--

	cmp.setup.cmdline({ "/", "?" }, {
		mapping = cmp.mapping.preset.cmdline(),
		sources = {
			{ name = "buffer" },
		},
	})

	-- Use cmdline & path source for ':' (if you enabled `native_menu`, this won't work anymore).
	cmp.setup.cmdline(":", {
		mapping = cmp.mapping.preset.cmdline(),
		sources = cmp.config.sources({
			{ name = "path" },
		}, {
			{ name = "cmdline" },
		}),
		matching = { disallow_symbol_nonprefix_matching = false },
	})
	local capabilities = require("cmp_nvim_lsp").default_capabilities()
	-- Replace <YOUR_LSP_SERVER> with each lsp server you've enabled.
	require("lspconfig")["lua_ls"].setup({
		capabilities = capabilities,
	})
end)

(Currently, I don't use Nvim-cmp; I migrated to Blink.cmp).

[echasnovski]

You need to use now or later to execute it.

That's not correct. Users don't need to use either of them. They can use them for a more robust config: later() delays executing its function until shortly after startup and both of them will catch errors and report them after all later calls are executed.

[therealjasonkenney]

Thanks, I figured out the problem.

Your example worked pasted into init.lua

It didn't when moved to after/plugins/nvim-cmp.lua, however so long as I put the add call back in init.lua it worked. I haven't had any issues with other plugins thus far. cmp must be sensitive to when it must be loaded.

Another bit I noticed (and it makes sense), MiniDeps.now within files in ftplugin load after MiniDeps.later in after/plugins. Which is a good thing :)

[therealjasonkenney]

@echasnovski yup, but he did give me a working file I could use to debug my issue, so it still helped :)

Liking the plugin thus far by the way.

[krovuxdev]

You need to use now or later to execute it.

That's not correct. Users don't need to use either of them. They can use them for a more robust config: later() delays executing its function until shortly after startup and both of them will catch errors and report them after all later calls are executed.

@echasnovski Apologies, you're right. There's no need to use now or later. I misspoke while explaining. I wasn’t paying enough attention to mini.deps and only did a little research on it. I haven’t migrated to mini.deps yet, I’m still using lazy.nvim.

(Reason: Mini.Deps lacks a window like :Lazy to view information or errors about repos/commits/refs or loaded plugins (to check whether a plugin is loaded or not). I would like something like :Deps for that. I know :DepsUpdateOffline already exists, but it’s not like :Lazy.)

Thank you for correcting me like this. :)