Michael Albinus <michael.albi...@gmx.de> writes: > Björn Bidar <bjorn.bi...@thaodan.de> writes: > > Hi Björn, > >> While trying to use tramp with SSHFS I noticed that the programs started >> using this method are still called on the remote rather than on the >> host. > > This is intended. > >> While the usual expectation for Tramp with SSH or SFTP is to operate on >> remote, for SSHFS this is usually not the case. > > For sftp, no remote processes are supported.
What doe SFTP have to do with this? Besides SFTP only works with GNOME or does it? >> Should there at least be an option to call programs started on the SSHFS >> paths locally or default to it? It does not make much sense to use >> ssfhfs and then call programs outside of it. > > The same program can return different values local and remote. Think > about 'hostname'. I was focusing on the caller and the target but I get the point. > A program which exist remotely, does not need to exist locally. > > And think about real life examples: A remote compilation or build environment. > > If you want to run programs locally, mount the sshfs file system, and use > the files with their local names via the mountpoint. The manual states that it mounts the SSHFS file system, which it does. Since SSHFS either through Tramp or otherwise mounts the file system it should be possible to transform the tramp path to the locally mounted file system and call programs on it. If the user wants to run programs on the remote SSH would be the better method. I think the confusion or the issue is that programs called when using the tramp-sshfs method don't use sshfs.
