Possibility to allow using local code base rather than download remote file as cache.

[Kailian-Jacy]

Thanks for your amazing work. distant seems the only way to invoke remote side lsp without installing neovim on the side. It works like a magic.

Is there any possibility to allow using the local project code with distant? By using local project code, I mean:

• Keep a copy of the project code on both sides, remote side and local.
• When things changed, async incrementally write to the remote.
• Edition, browsing, searching happens on the local files while only lsp working from the remote side.

So it helps:

• Migrate most experience like working locally. Tools like picker, file browser, nothing changed.
• No need to download cache from the remote side. There's some situations downloading from public network (like github) is easy while downloading over poor connection from remote side could be tough, or the codebase is very huge.

Imagined configuration:

    use_local_project: true,
    local_project_path: /path/to/local/codebase,
    remote_project_path: /path/to/remote/codebase,

[chipsenkbeil]

Hey there! Thanks for reaching out. The only way I see this being possible is if we offer the ability to mount the filesystem locally, having it mirror what is on the remote machine, while still running the other processes you care about like language servers on the remote machine.

There is a backlog idea of adding support to distant to do this: chipsenkbeil/distant#145

An example of a CLI that already offers this is https://duck.sh/, but it doesn't offer (in CLI form) the ability to execute remote processes, especially not ones like a language server.

So, definitely possible, but much more complicated to implement.