netman.nvim VS neovim

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.

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.