telescope-file-browser.nvim VS netman.nvim

EDIT: I found what I was looking for https://github.com/nvim-telescope/telescope.nvim and https://github.com/nvim-telescope/telescope-file-browser.nvim

I'm aware of telescope-file-browser.nvim, but it seems to only search through one directory at a time and not the full project at once.

for reference, what I want it to look like is what they have on the github repo for nvim-telescope/telescope-file-browser.nvim.

an alternative is to use telescope-file browser, which simply allows you to interactively go up/down a directory: https://github.com/nvim-telescope/telescope-file-browser.nvim

I use a lot of key bindings for telescope. A regular use of mine is to open telescope file browser with `` without a previewer, and `` (shift) with previewer. So I have `Layer + f` that sends `` on tap and `` on double tap. Same goes for telescope grep string, but a different config: `` does a live grep in relative folder and `` does a global live grep. Very useful when navigating big monorepos. This is how the layer looks:

There's telescope-file-browser.nvim

hop.nvim to easily hop to specific text with minimal keystrokes

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.