feat: default to vim.snippet for snippet expansion if available
#1820
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I think this is a perfectly reasonable fix, but it can cause confusion for people who use nvim-cmp without key mapping for snippets. I'll prioritize reasonable modifications, so I'll merge them. |
2 tasks
haunt98
added a commit
to haunt98/dotfiles
that referenced
this pull request
May 16, 2024
Thanks nvim 0.10.0 release See hrsh7th/nvim-cmp#1820
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Neovim v0.10 is introducing a native snippet engine. It seems like a good default to configure that for snippet expansion if it is available. Let me know what you think and if I should include any more details in the documentation!