dotfiles VS nvim-lua-guide

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.

Nvim Lua guide

My main struggles beyond a simple problem are just the inability to find a way to easily debug things and the general process for setting up a plugin. I mostly work with Python/Jupyter, some C and Lua/Bash scripts, and usually you can either write tests/print debug for smaller scale things or get some stack trace if you have an error. With Neovim development, it just feels like there's nothing more besides update plugin, try on neovim, fail, bash head against wall, and repeat, and that doesn't quite seem efficient or correct - I'm sure there's something out there that should make the process easier. I tried looking online but I haven't found many that really fit my needs (most of the resources here seem more targeted towards creating your own init.lua, and Luadev plugin's commands are all broken (:Luadev-RunLine and any other command keeps telling me I got some trailing space). I'm really just looking to see how to make a snippet library, but there doesn't seem to be much that helps me. If someone could let me know how they debug their plugin or point me to any external resources, please let me know!

I have no guidance for the first point. For the second, checkout the neovim lua guide or : lua-guide

A quick google search turned up this codeacademy class on learning to program in Javascript. I didn't vet the whole thing, but it appears to assume you know nothing, which is what you need. If you go through that, you can then consume one of the resources that /u/luascriptdev post to equate that back to Lua. Again, the concepts translate.