nvim-luapad VS vim-sendtowindow

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)

I have been using https://github.com/karoliskoncevicius/vim-sendtowindow

I use R with Vim. Usually the R script file is open on top and there is a :terminal window with R running below. And I use a small vim-plugin [1] for sending commands from the editor to the REPL.

This has a few advantages, major being that you can run any language with a dynamic REPL this way, without changing your setup. Or, you can even have two files, written in two different languages, open side by side with a corresponding REPLs running beneath each of them. The downside of course is that you miss on auto-completion and other integrations like that. These are not impossible, but you would have to torture your Vim setup quite a bit in order to implement them.

[1]: https://github.com/karoliskoncevicius/vim-sendtowindow

I often have to perform statistical tests on genomic data. Which in practice means running the same test on every gene (row of a matrix). Running it separately on each row is often slow, specially in R. So to speed it up I started an R package "matrixTests": https://github.com/karoliskoncevicius/matrixTests which is a lot faster and deals nicely with edge case scenarios (missing values, infinities, empty matrices, etc).

Another notable mention is maybe vim plugin "sendtowindow": https://github.com/karoliskoncevicius/vim-sendtowindow which implements an operator for sending text to another window. Handy for sending code in a REPL within vim ":terminal" buffer.