nvim-snippy VS vim-medieval

nvim-snippy?

I don't know about LuaSnip, but nvim-snippy can expand LSP snippets without using an auto-completion plugin.

I want to give some attention to the excellent nvim-snippy plugin.

I think it's a bug in Neovim; I ran into a similar (if not the same) issue, and I use neither nvim-cmp nor lsp-zero: https://github.com/dcampos/nvim-snippy/issues/90

I even wrote my own autocmd for auto-completion, which was a lot of fun and helped me learn a lot about Neovim. Together with nvim-snippy it meets all of my needs (so far).

there is nvim-snippy

For me it's about extra dependencies. It's not enough to just have Neovim, you also need Python and the pynvim package, plus whatever Python dependencies the plugin might have. It used to be a tradeoff worth it before we had built-in Lua, but now it doesn't really matter. The last everyday Python plugin I have is UltiSnips and I am currently evaluating nvim-snippy as a replacement.

I switched to snippy because I had the same problem

Snippy for snippets,

I recommend to use https://github.com/dcampos/nvim-snippy, I'm so happy with it

Most of the notes about the language are in an interactive readme with runnable code samples. It can be ran in 2 ways: - using nvim to evaluate code snippets inline using neovim with the mdeval plugin. Using FeMaco creates an editing floating window with rust-tools LSP attached and Treesitter attached. - using slides, an interactive terminal presentation tool

I agree this is a convenient approach! I use vim-medieval, which allows to run a code block and output to another code block, and your workflow fits very well with that plugin!

I guess someone else already sort of answered that. I.e., no, there are ways to do this without a plugin. But if you are not afraid of installing a plugin, then I find vim-medieval is a good solution here.