Bug: fallback_for = {} completely disables the source

[chrisgrieser]

In a recent update, the providers settings changed for the buffer-source, adding the fallback_for option.

While useful in principle, I personally prefer to have buffer to simply show its suggestions with lower priority instead of completely ignoring them in the presence of an LSP. I assumed that fallback_for could be disabled by passing an empty table:

sources = {
	providers = {
		{ "blink.cmp.sources.lsp", name = "LSP" },
		{ "blink.cmp.sources.path", name = "Path" },
		{ "blink.cmp.sources.snippets", name = "Snippets" },
		{
			"blink.cmp.sources.buffer",
			name = "Buffer",
			score_offset = -3,
			fallback_for = {}, -- empty to disable
		},
	},
},

But this is apparently not the case. With this config, I simply never get any buffer-suggestions. Whatever I tried, I could not figure out how to display buffer suggestions when there is also an LSP active.

A hacky workaround I found is to use fallback_for = { "Path" }, which effectively enables the buffer-source in most cases, since path does not return anything there is no /. But yeah, it's really a hacky workaround.

[chrisgrieser]

it appears completely leaving out fallback_for does the trick:

{
	"blink.cmp.sources.buffer",
	name = "Buffer",
	score_offset = -3,
},

I leave this issue open, since fallback_for = {} disabling the source completely nonetheless feels like a bug. Arguably it's maybe also a documentation issue, since it wasn't apparent from the default config, that you should simply leave out fallback_for