nvim-config VS hotpot.nvim

+1 for Hotpot, I love it. Here's my config: https://github.com/alexaandru/nvim-config 99.7% fennel :) I only have a single line of Vimscript (https://github.com/alexaandru/nvim-config/blob/master/init.vim) to load Hotpot, from there on, it's all Fennel.

+1 for Hotpot, I love it. Rewrote my config in Fennel (https://github.com/alexaandru/nvim-config), it worked like a charm. Also wrote a couple of plugins in Fennel (using the same, Hotpot), that was a lot of fun as well.

hotpot.nvim

There are some plugins out there that provide the Lua glue code (e.g. hotpot.nvim), but you will still have to depend on Fennel. I have not tried any of these plugins, so I have no idea how well they work. Neovim is not Emacs, and Lua is a fine language by itself, so that's what I prefer to stick with. And Vim script of course, it may be bad for plugins, but it's actually quite nice for configuration.

Hotpot: this is mostly just a Fennel compiler, but it is quite nice at that

Another method would be to use hotpot: https://github.com/rktjmp/hotpot.nvim. It's much simpler with what it does, doesn't include the macros and helper functions but you might prefer it. Here's an example: https://github.com/rktjmp/paperplanes.nvim

While there isn't an lsp, https://github.com/rktjmp/hotpot.nvim can give you diagnostics and https://github.com/Olical/conjure can give you cmp completions

I see there are 3 approaches Using aniseed: https://github.com/Olical/aniseed Using hotpot: https://github.com/rktjmp/hotpot.nvim Using plain fennel: https://git.sr.ht/~hauleth/dotfiles/tree/master/item/vim/.config/nvim/init.lua (this is just the one I found, lmk if theres a better version of this)

Hey y'all, I'm running into this issue. The solution is to remove the directory ~/.cache/nvim/hotpot. I would like to automate this when I upgrade my home environment packages as the issue seems to happen after a home-manager switch --flake --recreate-lock-file operation.

Here's a macro I wrote ages ago for my settings. Some might turn their noses up at doing this, because really you're just making a potentially leaky if not dysfunctional abstraction over nvim's actual API, but, well I did it for fun 🤷‍♂️.