pact.nvim VS hotpot.nvim

Macros are pretty attractive, because you suddenly feel really unconstrained by syntax. You can write a fennel macro to handle really weird non-uniform syntax which can be exciting. In the end, it's generally less hassle to go with functions though. Often I'll write a macro, then tune it, then tune it again, then realise I just need a function function, i.e this was all a macro initially but now the macro is simply sugar to let you go (await (my-func 10)), and even then it's pretty debatable if simply accepting a function name and arguments is particularly worse (i.e: (await my-func 10) where await is just a function), I really just wanted to retain the "call style" on the day I wrote it. They do give you a lot of power though, one of the first things I wrote after Hotpot was a macro to set keymaps to functions directly, with closure scope which would have been pretty annoying without the macro - possible as the macro is just lua in the end, but pretty annoying, annoying enough that most people didn't bind "one shot" functions. I think that is where macros really shine, allowing you to actually patch short comings, not just alter syntax. Apart from that - which is now deprecated by 0.7 - I think I have one other macro in my config which ... could actually just be a function.

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 🤷‍♂️.