Hi, I just upgraded to Sublime 3.0 build 3170 and realize a bad bug that renders sublime unusable for me.
I cannot open mounted directories. Instead of opening up the directory with the source code it opens a “file” with the same name.
My workflow is to mount directories to a remote dev server from my OSX laptop. I code on OSX but build in the native environment.
Update: I managed to download “Sublime Text Build 3143” and install it. Build 3143 does not have this bug!
sshfs although I don’t think that should have a significance.
sshfs -o reconnect <username>@IP:<remote_dir> <local_dir>
Reverting back to the 3143 makes it work again.
Apparently it does, in some sense, since normal hard drives and samba shares seem to continue to work properly. The two things that changed in 3170 regarding the filesystem for Macs is support for case-sensitive filesystems and some improvements in regards to handling symlinks.
@wbond I can’t explain this but after reverting back I wanted to see if I could troubleshoot it further so I reinstalled the latest build again and now it works. I don’t know what this hickup was. If it happens again I will try to see if I can troubleshoot it better.
latest version upgraded to:
