gh.nvim VS mini.nvim

I'm not aware of any plugins that does this. Maybe these can do it but I'm not an avid user of either. https://github.com/ldelossa/gh.nvim https://github.com/pwntester/octo.nvim

this is octo, which i was not referring to -- i was referring to it's cousin which seems like the ideal for me https://github.com/ldelossa/gh.nvim

Another option to check out: https://github.com/ldelossa/gh.nvim

Shoutout to Louis DeLosSantos for his awesome gh.nvim plugin shown in the video.

Something like gh.nvim?

It takes a "commit-wise" approaching, which is useful in most professional OSS projects where commits are the defining structure of the pull request.

Theres a good amount of initial features outlined in the demonstration video.

Gh.nvim is very new, and probably has a fair amount of bugs still, however I use it daily at this point. Could use some testers to find bugs/report issues/contribute fixes etc.

Code is here: https://github.com/ldelossa/gh.nvim

Demo is here:

https://github.com/ldelossa/gh.nvim/pull/4 just finished up a quick run on multiline support. going to play with it for a day or so then merge, feel free to try it out.

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