You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using neovim-qt v0.2.16.0 and connecting to a neovim instance of v0.7.2 running on a remote machine via ssh socket forward.
The nvim_gui_shim plugin was loaded, so the Gui* commands could be found. But when using the command GuiTreeviewShow, it displays the files on local machine instead of the files on remote machine
The text was updated successfully, but these errors were encountered:
It makes sense based on how the code is designed: Qt parses and builds the TreeView from the local filesystem. The logic is separate from the Vim/Neovim infrastructure.
I can't think of a simple way to make Qt aware of the remote machine's filesystem. Not to mention, doing so might open up a whole new level of complexity and potential security issues.
Yeah, I agree. The tree view was never designed for this. Currently it only forwards the current working directory.
A full solution for this would be to implement vimscript to forward the directory contents to GUI instead of just sending the path, but this can be expensive (large folders and so on).
For reference, these are the locations where the event is sent and used:
I'm using neovim-qt v0.2.16.0 and connecting to a neovim instance of v0.7.2 running on a remote machine via ssh socket forward.
The nvim_gui_shim plugin was loaded, so the
Gui*
commands could be found. But when using the command GuiTreeviewShow, it displays the files on local machine instead of the files on remote machineThe text was updated successfully, but these errors were encountered: