dotfiles VS nest.nvim

I find legendary.nvim a lot more versatile, and the author has his own config for it on GitHub, look at his dotfiles repo: https://github.com/mrjones2014/dotfiles/tree/master/.config/nvim/lua/my/legendary

No problem, let me know if you have questions. Dotfiles repo for reference.

Sure! Here's how I configure legendary, which imports my keymaps, commands, and autocmds.

That’s pretty much what I do

I have a few things that depend on load order as well. I keep a very minimal init.lua which just requires a few other modules. Plugin configs I keep in ~/.config/nvim/lua/configure/plugin-name.lua and then they get installed and configured from ~/.config/nvim/lua/plugins.lua. Feel free to browse my config: https://github.com/mrjones2014/dotfiles/tree/master/.config/nvim

You can see my config here: https://github.com/mrjones2014/dotfiles/tree/master/.config/nvim

However, I will shamelessly plug my plugin nest.nvim which I wrote to have a nice API to manage keymaps in Lua :-)

(shamelessplug) nest.nvim supports binding lua functions directly while also cleaning up your kenind code ;-) (/shamelessplug)

I will shamelessly plug my plugin nest.nvim here - it is a small lua utility to set your keybinds in lua config in a nice syntax. It also supports binding lua functions.

A few other plugins exist that provide similar functionality, like nest.nvim and nvim-cartographer, but what differentiates Mapx is that my goal was to build upon and improve Vim's familiar style of creating mappings that many of us are used to.

I just released version 1.1 of nest.nvim, adding several new core features:

(shameless plug) May I recommend nest.nvim to manage your keybinds in Lua? :-) (/shameless plug)

nest.nvim ;-P

While that cannot work for "normal" bindings when you pass `expr`, I could actually handle that special case (`expr` + `lua` rhs) within nest.nvim pretty easily 🤔