Sources v2

[Saghen]

• Closes Trigger with only list of providers #386
• Closes Deselects after quickly pressing keys #219
• Closes use ALL instead of ANY for fallback_for #328
• Closes New provider attribute: fallbacks #331
• Closes Source timeout and non-blocking requests #312
• Closes Custom sorter #454
• Closes Better way to handle multiple sort criteria? #444
• Closes Support blocking trigger characters per filetype #372
• Closes Allow adding providers add-hoc after blink.cmp has been setup #475

Notes

• Enabled providers should be reworked, ideally with a simple way for per-filetype sources
• How to handle sources returning multiple responses?
  • Do we immediately show on the first response? Would this cause weird behavior with the LSP source when there's multiple clients giving completions?
  • How do we handle async sources? (i.e. copilot)
• Is source defined keyword regex necessary? Can they instead use enabled since it now runs before each call to get_completions? CC @stefanboca

[stefanboca]

With regards to keyword pattern as they're used in nvim-cmp, my understanding is that sources are not disabled if a match is not found, but rather that matching the keyword pattern is used as another trigger in addition to trigger characters. So to replicate nvim-cmp's mechanism, using enabled is not enough.

Also, I believe nvim-cmp uses lua patterns, not regex.

[stefanboca]

I also think that nvim-cmp uses the keyword pattern to define the completion context if a match is found, for reference.

[Saghen]

Ahh super insightful, thanks

matching the keyword pattern is used as another trigger in addition to trigger characters

I'm thinking we could do something like should_trigger to cover this case

I also think that nvim-cmp uses the keyword pattern to define the completion context if a match is found

And we could ignore this, since sources could mark themselves as incomplete if the default context isn't fine-grained enough for them. We could also expose a helper for getting the match before the cursor for those that need this

[Saghen]

Skipping #313 for now, I'm thinking the existing APIs could be enough. Maybe I'd need to see a specific example where it's needed