dotfiles VS nvim-lua-guide

Thank you so much!! From my research it used to be documented in the wiki but was removed, and I was not using the option nesting within the completion key. Looking at your dot files made it clear how to use it, may help someone else:

I'm following along with this post and the associated dotfiles.

I call it with an autocommand on save here https://github.com/lukas-reineke/dotfiles/blob/master/vim/lua/lsp.lua#L124-L129

I have a format on save setup with efm that I'm pretty happy with https://github.com/lukas-reineke/dotfiles/blob/master/vim/lua/lsp.lua prettier is in there as well.

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.