nvim-snippy VS .config

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

I've done my best to keep my config simple and sane: https://github.com/heygarrett/.config/tree/main/nvim

One option the docs don't list is using an autocommand, which is what I do because I overrule the indentation options for all file types.

I use a combination of guess-indent.nvim and :h listchars. Here's how I use them together in my config.

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).

I'm late to the party, but I did configure my statusline without a plugin: - Screenshot - Config

I added an autocmd to make it automatic.

I learned a lot, and I created my own automated workflow for sessions that I’m quite happy about. I think the best part is it may not cover every use case I encounter, which means I get to keep learning and I get to become more familiar with a tool I use daily.

I use this in my custom statusline config, which you can see here.

This is how I currently configure my indentation. The autocmd overrides anything set by the ftplugin files during startup, and that's the easiest method I've found keep my preferences across every file type.

I think the built-in filetype plugin files are sourced after your vimrc. I got around this by adding an autocmd to re-set my indentation preferences after the ftplugins are loaded.