I’ve noticed that when opening files remotely (Interarchy, Transmit, etc.) that have been previously opened by Sublime 2, that it retrieves a cached version of the file instead of the current state of the file. This is particularly problematic when working on remote files that may be modified by another editor. A restart of Sublime 2 is required to ensure that it has a fresh copy and does not destroy the edits made by another application or user. Any suggestions?
Session cache too sticky?
eelco
#2
sorry for the bump, but haven’t found any better fitting problem.
i’ve sort or less the same problem.
My workflow:
I’ve this problem using OSX (both 10.7 & 10.8)
- login on a remote server using Transmit
- edit files
- close st2
- refresh folders
- start editing again
Between steps 3 and 4 another person was editing on the same file. These changes weren’t in the files I opened the next day. So I got a lot of differences once i did a commit. How can I get rid of this?
0 Likes
bizoo
#3
Did you save the file before closing ST2 ?
Hot exit feature of ST2 store the current file state in the session, not in the actual file.
Maybe is it the problem here…
0 Likes
eelco
#4
I did save the file—I always do. I don’t rely on autosave functions. So that isn’t the case.
0 Likes
eelco
#5
Okay, further investigations showed me that the problem relies within Panic’s Transmit. ST2 seems to work as expected.
0 Likes