nvim-luapad VS mini.nvim

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)

This is essentially a tagline of mini.move.

Just as the others suggested, oil.nvim solves this outta the box. I freaking love it (here my config in case ya need it). Apparently also mini.files handles this by default

You mean backwards seeking text objects? You can get those with mini.ai https://github.com/echasnovski/mini.nvim/blob/main/readmes/mini-ai.md

I would like to offer you to join me in saying late greetings to this autumn with a release of mini.nvim version 0.10.0. It is mostly about introducing three (quite feature full, dare I say) modules and minor updates of existing ones.

Last night I cleaned up all the dead code in my config and realised that mini.nvim has to be the single best plugin that I've used. I have a couple of other favourites but this collection has been so consistently good that I wanted to give some thanks to the juggernaut that is u/echasnovski! Thanks for all the work you plugin authors and core maintainers put in to make this editor what it is <3

For example: I spent a lot of time configuring file tree plugins to have the same sorting as VS Code, tweaking their icons, etc. But then I realized I barely used the file explorer at all, and now I'm super happy with the minimal approach of mini.files. I had similar experiences with other plugins that were just adding "fluff" instead of the functionality I was looking for.

Around two weeks ago I've announced the release of mini.files - a file explorer module of mini.nvim with column view navigation and "edit text to manipulate file system" design. This resulted into a great feedback from the community, much of which turned into new features.

A mini.ai textobject specification that you can use standalone