This sort of behavior is unfortunately fairly common in FUSE-based file systems, especially those which depend on an SSH connection.
If you want something a bit more robust and easy to use, you can try something that I've been working on called 'xeno' (https://xeno.io
). I was similarly having problems with SSHFS (more to do with a shoddy connection than the editor acting weird), so I put together this Git/SSH mashup as a replacement for SSHFS. It will allow you to open up files/folders in Sublime Text (or any local editor really) over an SSH connection, and automatically synchronize changes to the remote machine. You can even start your local editor from *inside* an SSH session and have it continue to synchronize changes to the remote after you quit the SSH session. It should work on almost all POSIX systems (I myself use it from OS X to connect to Linux machines and edit files in Sublime Text).
What it does is generate an out-of-worktree Git repository of the files you want to edit on the remote machine, and then clones it locally and uses Git over SSH as a transport/synchronization mechanism. This does not interfere with any existing source control, and it also does not require you to use any existing source control. And because it's built on Git, it's extremely fast and supports automatic merging of files that might be changing on both ends, unlike SSHFS which will just clobber any files with older timestamps.
Plus, because you are editing local copies of the files, you don't end up depending on a virtual filesystem which has rather unpredictable behavior, and you can even drop offline and have your changes automatically pushed to the remote when your connection comes back up.
It's also free and open source
, and I'd really love some feedback.