pact.nvim VS nvim-lua

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.

I recently converted vim-tmux-navigator to lua via a simple function and using A-hjkl\ binds (which has no conflicts) instead of the default C-hjkl\, feel free to reuse my code, relevant commit.

source: https://github.com/ibhagwan/nvim-lua/blob/main/lua/lsp/rename.lua

I guess this is a preference thing, I would consider my config my config highly customized and pretty advanced, it has almost 8k lines of code, I don't fiddle with it as much as when I just converted to lua but I still update ocasionally and I find lua perfect for the job, instead of macros I just create small lua functions in order to avoid code duplication (where applicable).

I'm not just giving you complements to boost your morale, I've seen your code first hand, I've used feline (we even interacted in issues) and also copied your archived nvim-reload code into my config and can recognize a good programmer when I see one.

Technically all you need to do is set package.loaded[module] = nil for all the modules you wish to reload and that's why my modded version does, it reloads all your entire neovim config and all the plugins listed in the linked init file.

FYI, just added this to my config with a slight twist (resize back once I'm done), this so great :)

My config isn’t a “permade”, it’s not meant to be a solution for anyone other than myself, nevertheless you might find it useful for plugin selection and some cool functions.

You can view my setup here.

My own version of Embark colorscheme and feline.nvim, my configuration can be found here

Btw, if anyone wants the “evil-line” equivalent config for feline you can find it here