nvim-luapad VS nvim-lua-guide

there is this plugin: https://github.com/rafcamlet/nvim-luapad

Ah yes, finally a question I can answer. There is no easy way to do this. This was the first big problem when I started working on: luapad, and I dealt with it, by creating a temporary files, attaching lsp to them, and removed them right away from the file system. But later on it started to cause some problems (can't remember what they were now) so ultimately the temp files are not deleting until neovim is restarted.

I was wondering how the hell you did it. There are no autocmds for window resizing. I was trying to figure this out for preview win for nvim-luapad and I gave up. But this timer idea... aren't there any performances issues?

This is a work in progress, but for 'mini.indentscope' I currently settled on using 'plenary.nvim' with helper for creating full child Neovim processes and testing directly extmarks (source; original idea is from rafcamlet/nvim-luapad). Eventually I plan to convert these helpers and 'plenary.test_harness' into something like 'mini.testing' (but only after yet another ready but being alpha-tested jumping module 'mini.jump2d' :) ). Hope that'll help now.

Hi! I think I have exactly what you are looking for. Check the spec directory in the luapad dev branch https://github.com/rafcamlet/nvim-luapad/tree/dev/specs. I am using RPC to send instructions to another nvim instance and then check the results, restarting it between each test for clear env. It may be a bit messy, but I'm currently working on extracting this logic to a separated plugin.

Here's the other lua/neovim dev plugin I was thinking of that might help testing smaller portions of your code https://github.com/rafcamlet/nvim-luapad

Dude, I like your plugin, but please: do a gif or a video about what this plugin does (nvim-luapad do this and I know exactly what this plugin does)

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.