-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose nvim-cmp preselect option #670
Comments
Use I understand that this is a little confusing, I'll add a type-checked option for future reference when I get back to my system. |
@NotAShelf That is useful info, I was wondering how that was done. I think "none" should have worked as well because However, neither seems to work correctly. |
If there aren't any errors, then my guess would be on a configuration option conflict. Starting neovim with the init.lua in the store won't work because plugins are missing in the environment. Your best bet would be isolating nvim-cmp configuration, and creating a minimal standalone nvf environment to mess with nvim-cmp only. |
🏷️ Feature Type
API Additions
🔖 Feature description
I've been trying to use NeoVim with autocomplete but the behavior I have always preferred is to not autoselect a completion until the tab key is pressed. That way if I type something quickly that ends in Enter, it does not insert a completion.
My old config had lsp-zero (which seems deprecated)
I believe the correct way to do this without lsp-zero is
I found this here: https://www.devonmorris.dev/posts/nvim-cmp-preselect/
I tried the following with NVF:
Somehow this still doesn't work. The completion menu is visible but no item is selected, pressing enter selects the first item instead of inserting a newline.
Somehow the preselect option is not taking effect.
Am I doing something wrong?
Could this just be exposed via NVF to make this a little easier?
✔️ Solution
I would like an option to configure the preslect behaviour of nvim-cmp
❓ Alternatives
If this can be done without exposing a nix option, I'd be happy with that solution too.
📝 Additional Context
No response
The text was updated successfully, but these errors were encountered: