-
Notifications
You must be signed in to change notification settings - Fork 0
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
Snippets! #2
Comments
I think snippets.nvim deserves being moved to the "In Progress" tab :) |
Good point; I've updated the state of all the ideas for which we had a documented partial/in-progress implementation. |
Actually, (Otherwise it'd be worth specifying what precisely counts as a "Done" plugin...) |
Cool, sounds good. |
That should probably be done regardless, right? |
Yeah, that's a good idea. I'd suggest something like "A wish is 'granted' when there exists a feature-complete, stable plugin implementing the wish's idea". Does that seem reasonable? |
Yeah, that makes sense. (The readme isn't up-to-date, but @norcalli called it basically done on Gitter today.) |
It has a wiki now, too. |
What?
What it says on the tin: a pure Lua snippet engine.
Why?
The major snippet plugins (UltiSnips, neosnippets) are remote python plugins, which adds a dependency. There's also https://github.com/hrsh7th/vim-vsnip in pure vimscript, though, but Lua should have significantly better performance and be more hackable. It should support the basic features: snippet management (either in its own format, UltiSnip/neosnippet format, or LSP); snippet expansion (including nested placeholders) and ideally transformation.
Potential existing implementations:
https://github.com/norcalli/snippets.nvim, which is useable but still lacks a few of the above features.
Potential pitfalls:
Ideally, the expansion should be based on extmarks, but that requires the PR https://github.com/neovim/neovim/pull/12249/files to be merged first.
The text was updated successfully, but these errors were encountered: