Since the new 3.2 version of ST I’m noticing many different behaviours concerning the interaction with filesystem (specifically with NFS).
The issues are particularly annoying when working with virtualized environment (our default setup) and none of them was happening with versions < 3.2.
What happens to me (on MacOS 10.14) is:
- while in the past I could connect/disconnect volumes without any problem, regardless of SublimeText having any file open on them, now when I try to disconnect a NFS volume, I get an annoying The disk “www” couldn’t be ejected because “Sublime Text” is using it.
Now if I can’t temporary quickly switch to another virtualbox; SublimeText forces me to close the project with all its files, and then disconnect the volume; to then allow me to actually re-open SublimeText and open a different project
. - when there are loaded files from a NFS, in SublimeText, if anything happens that disconnects the NFS volume then SublimeText will crash completely and needs to be restarted (but it lost all the undo history, and closed all the open files that didn’t have pending changes to be saved).
This is pretty annoying and can happen quite randomly. Actually it happens different times per day because of simply putting my Mac on sleep for a little longer (lunch break, go to the toilet, etc.). - (unrelated to NFS) often I find out that the console doesn’t open anymore using the mouse; one has to use “View”->“Show console”. And also plugins stop working, without any error or report in the console. It simply silently fails calling plugin commands and will start working again just after a restart
I just realise now how I loved ST for its unobstructiveness and its stoic endurance without crashing.
Since the last release it is soooo sensitive and picky to NFS volumes. And it feels like quite a regression.
I am wondering if these are recently introduced bugs or what led to touch the code dealing with the filesystems, and why was that needed (I suppose stuff changed to ease the git integration?)
I’d like to know more about it and if there is active work on that or it is probably gonna stay like this for the future releases.