snippet-converter.nvim VS LunarVim

Afaik there is nothing built into Neovim that can do this. However, I have required this for one of my plugins so I created it. Here is the link: https://github.com/smjonas/snippet-converter.nvim/blob/main/lua/snippet_converter/utils/json_utils.lua. Feel free to use it!

Also, my snipmate parser is probably a good starting point since the grammar is relatively simple: https://github.com/smjonas/snippet-converter.nvim/blob/main/lua/snippet_converter/core/snipmate/body_parser.lua

Moved to LuaSnip with the aid of snippert-converter, and it's good. No performance issues, easy to setup with nvim-cmp and works well. Would recommend.

Please check out my plugin snippet-converter.nvim which will hopefully save you a lot of time! I have put in a lot of effort to handle as many edge cases as possible so you don't have to worry about line breaks and stuff. Cheers! (Note that this plugin currently only supports vscode_luasnip as a target format not "native" LuaSnip snippets in Lua but VSCode-style snippets should cover 99% of your use cases).

Nice article! Luasnip also supports snippet priorities btw so you don't need to delete them. You could also automate the conversion of the snippets using snippet-converter.nvim (hope no one minds a bit of self-advertising here ;). That should surely speed things up a bit.

No you would need to convert the snippets to VSCode or SnipMate format first. You can do that using a plugin like snippet-converter.nvim (disclaimer: I am the author of that plugin). Simply set the output format to vscode_luasnip or snipmate_luasnip.

Shameless plug: you could also try my plugin https://github.com/smjonas/snippet-converter.nvim which can handle many more edge cases :)

I am excited to announce the release of my first own plugin snippet-converter.nvim that I've been working on for the last couple of months!

You can try my plugin snippet-converter.nvim, it has not been officially released yet but it's already functional. Sorry for the self-promotion but this seems to solve your problem :) It allows you to write your snippets in UltiSnips format and convert them to VSCode snippets.

There does not seem to be a good way to do this at the moment. However, you might be interested in my plugin snippet-converter.nvim that I've been working on for a few months now - the issue you described is one of the use cases of the plugin! It's already usable but there is still some stuff that need to be worked on... If that's done I'll definitely make an announcement on this sub (hopefully in the next weeks) :)

LunarVim

I would suggest to start getting into vim by first trying out popular vim keybinding plugins available on your favorite code editor and get used to those first. Then, if you want to dive deeper into the power of Neovim, try out popular configs like LazyVim, LunarVim, NvChad... Taking Neovim from a mere text editor to a full-featured IDE with features like intellisense, debugging, testing, etc... on your own takes quite a lot of work and configuration.

I used Helix for a while due to its support for LSP out-of-the-box, which my Vim config at the time couldn't live up to. I switched back to NeoVim after finding LunarVim[1] which had everything I was trying to get setup in my own config.

[1] https://www.lunarvim.org/

I'll admit I didn't look into it, but Helix sounds like something like LunarVim (https://www.lunarvim.org/)

Personally I much prefer that the editor NOT ship with something like that by default, especially when it's so easy to set up. I have several different vim config I use, including a pretty bare-bones one for headless systems, and I much prefer the ability to customize something very specifically.

Build tools that can compose together, rather than a single do-it-all tool. That is the power of the low level editors vs IDE's.

I can't comment on any implementation details, but at least with LunarVim (which I use for daily coding), a slowdown when interacting with LSP is very noticeable. Some others have attested to this on a GitHub issue.

I'm not doubting your experiences with the lack of a slowdown, but there is truth that others do experience it. That might be more of a problem with LunarVim itself rather than Vim, but how likely am I (as someone who would like to avoid what he calls "config hell") or other newcomers to avoid whatever pitfalls there are, if a distribution designed for ease of use by people who know better fall into them?

https://github.com/LunarVim/LunarVim/discussions/3359

Anyways, although i have not used them, LazyVim and LunarVim comes highly recommended. You can try these and see what suits you .