nvim-lua-guide VS kickstart.nvim

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.

I found this repo the other day with a list of good resources on it. https://github.com/nanotee/nvim-lua-guide

I recently started coding with Neovim using kickstart.nvim as the template for my editor configuration. I downloaded the python-lsp-server package using Mason, but I was disappointed to discover that the IntelliSense on my third party dependencies didn't work. The LSP was resolving to my global Python installation, which did not have the packages from my virtual environment (venv) installed.

I also suggest against using distributions. Instead of learning how to configure nvim itself you're learning to configure that specific distro.

I suggest to take someone's lua config and start from there. Kickstart.nvim is a good one: https://github.com/nvim-lua/kickstart.nvim

1) the option I wouldn’t chose, use Kickstarter. It’s a minimal starter config, using a single init.lua that helps you build a config slowly. https://github.com/nvim-lua/kickstart.nvim

After you’ve gotten used to that, I would start using Neovim using kickstart.nvim as a base and building your config off of that. It is a fantastic starting point for your first config and has LOTS of comments to help you understand what is going on.

If you prefer neovim, you should try https://github.com/nvim-lua/kickstart.nvim

I highly recommend Lazyvim for if you want to have a VSCode (ish) like experience that still exposes you to configuring in Lua. Or Kickstart.nvim if you want a more "from scratch" experience

In case it is helpful, I am using kickstart.nvim with only minor modifications.

One of the project goals is to become something like kickstart.nvim. Or, to be a reference if someone doesn't know how to do something.

i got a neovim config based on kickstart.nvim with a total of 9 additional plugin even with that small config i get terrible delay in insert mod (about 3 second) when editing middle sized files (~600) lines what i am doing wrong ?