-
Notifications
You must be signed in to change notification settings - Fork 17.4k
atom do not reload file on sshfs when modified by external program #13717
Comments
This comment has been minimized.
This comment has been minimized.
Same issue, if I open a log file from server and then re-download and open that file from server using Filezilla, atom shows the contents of old file instead of updated file. Hard to imagine why it is this way or not fixed yet , if bug. |
This comment has been minimized.
This comment has been minimized.
You need to turn of cache on sshfs. |
Did anyone find a way to resolve this? Or an alternative way of working with an sshfs share? |
same issue here sshfs cache off did not work for me |
Thanks for your contribution! This issue has been automatically marked as stale because it has not had recent activity. Because the Atom team treats their issues as their backlog, stale issues are closed. If you would like this issue to remain open:
Issues that are labeled as triaged will not be automatically marked as stale. |
still the case in Atom 1.40.1 x64 on Ubuntu 18.04 (installed from snap): files changed externally are not automatically reloaded by Atom. Dangerous behaviour. Should be fixed asap. |
Same here, sorted a file open in Atom from the bash prompt, expected Atom to alert me to the change and to offer to either save or reload. |
Atom 1.40.1 on Ubuntu 16.04, the same issue. |
Prerequisites
Description
atom does not reload a file which is modified by an external program when the file is on a folder mounter by sshfs. This is very common with command like
svn up
, which means that you are overwriting all the changes made by other contributors.I don't know if there are packages which does this, but I think this should be the default behaviour of any editor, at least atom should warn you.
Steps to Reproduce
Expected behavior:
atom should reload the file after svn up
Versions
Atom : 1.12.7
Electron: 1.3.13
Chrome : 52.0.2743.82
Node : 6.5.0
Additional Information
emacs does
The text was updated successfully, but these errors were encountered: