dotfiles VS lazy-require.nvim

Mostly shell hackery and a bunch of more convenient selection, copy and paste functionality plus extensive documentation like the (supposedly) undocumented line selection operator g_ https://github.com/matu3ba/dotfiles/

I am relative satisfied with mine, although I still dont have a working solution for (vendored) project search and custom sources on keypress for completion is also missing (command completion breaks C-l/Tab for file completion): https://github.com/matu3ba/dotfiles/tree/master/.config/nvim

My config consists mostly of documentation, where you can take a look. I have a plugin as git dir I do include for company stuff, because of network shenanigans packer can not handle. https://github.com/matu3ba/dotfiles

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

Otherwise, you can check my setup, but I did not setup snippets yet https://github.com/matu3ba/dotfiles

Thats how it works. You could reduce the amount of plugins or document them for quick lookup. I do this extensively in my dotfiles https://github.com/matu3ba/dotfiles/blob/master/.config/nvim/lua/my_packer.lua

For my config I did write a pile of notes of the default keybindings because I found no good and dense note collection on (all) default keybindings and Vim+Neovim hardcodes them with only an annoying way to search exact the exact keybinding. https://github.com/matu3ba/dotfiles/tree/master/.config/nvim

If you want a more minimal example for explanation, you can check my cmake template: https://github.com/matu3ba/dotfiles/blob/master/templates/CMakeList.txt

I find this cleaner to do in lua without vimscript calls, see here.

Normally you can use tjdevries/lazy-require.nvim/ but sadly neotest's function is hidden under 2-depth table.

But FYI, there might be a name clash with https://github.com/tjdevries/lazy.nvim :-/

Here is my understanding. There is a penalty for using vim.cmd or accessing vim functions. They supposedly will only run as fast as they would in vimscript it's self so not very fast. Not sure of any of them are actually functioning different from their vimscript implementation. Vim.cmd likely is even slower since it requires the extra overhead of persing the vimscript. For lazy loading take a look at https://github.com/tjdevries/lazy.nvim .