Apparently this error is ERROR_BAD_NET_RESP “The specified server cannot perform the requested operation”
Generally speaking, any file notification API I’ve used doesn’t work across network shares and the like (eg. a mapped SharePoint drive). In this situation Sublime Text should probably be falling back to polling instead of using ReadDirectoryChangesW.
I think this is what Jon tried to do with this latest release but once the error occurs polling fails and the notification system stops working as well. This could be something at the OS level such as Windows serving up a cached version of the file once the error occurs. I have not tested, just speculating.
Ahh. I see. Looks like I misread the release notes.
Also speculating here, as I’m not actually Windows user. But having helped maintain a cross-platform file system notification library, I can certainly appreciate how difficult it is to get this stuff right.
@jps Thanks for another stellar dev build.
One minor annoyance is that every update seems to rewrite the User Preferences.sublime-settings.
To work around this, I’ve decided to put my config in .git so I can easily revert. So it’s not a huge problem for me anymore, but certainly not great in terms of usability.
Btw, I’m really looking forward to what plugin developers build with the new panel APIs. Cheers.
Sublime Build 3101, OS X 10.11.3
I certainly agree. I’m forced to implement changes for multiple clients on a daily basis. Often times they contradict each other and I must find the common ground that will make both clients happy but still provide a consistent and fluid user experience for all users.
Software development is no easy task. I can only imagine making so many developers happy with new functionality and bug fixes is a huge undertaking for Jon. My hat goes off to you @jps. I can only imagine what your daily workload is like. I am only dealing with 15 or 20 clients all making requests and I am pulling my hair out. I cannot imagine handling the load you get with Sublime. I think I speak for the masses when I say that your efforts are certainly appreciated.
That’s right - polling won’t happen for any directory that we’ve successfully received change notifications for. I’ll change it to be more pessimistic about the probability of continuing to see change notifications.
Updates don’t rewrite User Preferences, but any automatic changes, either from the UI (e.g., adding a word to the dictionary) or from the API (e.g., a plugin calling Settings.set() on the User Preferences) will cause them to be rewritten.
One work around here is to place your hand edited Preferences.sublime-settings file in a separate package (ZUser perhaps). This way the file will never be programmatically modified.
This may or may not be triggert by an update specificaly, but most certainly it will be triggered by every plugin changing your user preferences with the sublime.save_settings API since that will dump the settings in lexicographical order (object keys and list items) and also remove comments, since they are not stored when parsed.
This is part of a bigger problem, also tracked here: https://github.com/SublimeTextIssues/Core/issues/426
Oh dear! Yes, you’re right. I missed this part!
Now it works, thanks!
(the package wasn’t outdated, but I simply ignored that folder… don’t ask why!)