On 24 Aug 2016, at 2:40, Carpii UK wrote:

I've since noticed this only happens after getting an Atomic File Save

failure, so its all kinda linked back into the original problem I was

having with Atomic Save failures, the difference is I;ve since tried to

reconfigure SMB a bit

So even after you disabled the support for mangled Windows 95 names, you are still seeing failure from atomic saving?

I plan to try and branch TM to disable Atomic Saves for certain paths (like

/Volumes/*)

I've dug through the source a little, but this change doesn't seem trivial,

so any gotcha's or pointers would be appreciated

TextMate reporting “Atomic Saving Failed” is a bit of a misnomer.

I think I described it earlier, that on a network file system it would create a new /path/to/file~ and then run mv /path/to/file~ /path/to/file.

So what you probably want is to instead open the original file directly and just overwrite it, so you are not disabling a feature, your changing the code (to be less safe).

I mentioned some tests in the thread about atomic saving, if it still fails for you, evne with the name mangling support disabled in SMB, it would be good to get the results from these tests, as then TextMate could maybe handle the issue better.