vidir VS netman.nvim

I just learned about vidir [1]. Emacs Dired [2] can rename & delete files by editing the buffer directly, and let's say I was thrilled when I saw someone replicated that behavior as a general Unix tool.

[1] https://github.com/trapd00r/vidir

[2] https://www.gnu.org/software/emacs/manual/html_node/emacs/Wd...

I'm sticking with (and would highly recommend) vidir over this.

If this sounds familiar, that's because it was not my idea! Almost one year ago exactly, dirbuf.nvim was announced and it blew my mind. From what I can tell, the idea for dirbuf actually came from an earlier plugin called vidir, but this was the first time I'd seen it and, to be fair, its execution is fantastic.

vidir for the win!

You navigate Dirbuf with your cursor, pressing enter to open a file/directory. Editing in Dirbuf works like vidir where, when you edit a directory, you get a list of the files, directories, etc. in that directory and can edit them like text. Then when you save the buffer, all the files and directories you added get created, everything you copied gets copied, everything you renamed gets renamed, and everything you deleted gets deleted.

Hello Neovimers :) I posted this on the netman repo as well but I just wanted some opinions from users who use netman.

Lazy self promotion of netman.nvim which is designed to give you browse (and edit/read access) of remote systems without actually needing any configurations on said remote systems :)

I haven't been super active lately but Netman.nvim is my attempt to give neovim a solid remote editing experience. I've been taking a bit of time to myself though but it's still relatively stable for ssh and docker.

If you are really interested in doing this yourself with loop, you should take a look at either plenary.job or netman.shell (I made the latter) as both are very well documented.

If there are any users of Netman already that also use windows (or users of Neovim that want to use Netman but can't because they are on a windows machine), please checkout the windows-compat branch!

Does that not write out to the current pty? That is an issue I have been facing with generic ssh support in netman. I have yet to come up with a decent solution to it :(

A quick bullet point list of features that are included in this point update - Mostly complete Neo-tree integration - Moving files and directories between hosts (including between docker containers and ssh servers) - Auto opening your remote "home" directory in ssh - A complete rewrite of how our "integration" with neovim works - A completely new logging system - A new event system

The password issue is currently something I am looking to address in netman though exploration into the area has proven unfruitful so far :/

Netman supports remote editing of files over ssh.