You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition a mechanism that does not overwrite the original behavior of e.g. <TAB>, respecting existing bindings should help. For example, a new <TAB> binding could pass-through to the existing binding and only trigger the llama completion if there are completion candidates.
The text was updated successfully, but these errors were encountered:
The hardcoded keybindings may clash with other plugins that make use of e.g.
<TAB>
like autocompletion plugins (blink, cmp, etc.).A nice solution would be to make those hardcoded keybindings configurable
In addition a mechanism that does not overwrite the original behavior of e.g.
<TAB>
, respecting existing bindings should help. For example, a new<TAB>
binding could pass-through to the existing binding and only trigger the llama completion if there are completion candidates.The text was updated successfully, but these errors were encountered: