Just to chime in here and give some input:

I had this issue appearing on my machine as well and it only happened when editing files on a mounted drive located in a VirtualBox guest (Debian fwiw). I had other issues with that setup (file name case sensitivity, versioning also locking up, filesystem watchers not working and what not) that led me to reversing the setup. I now have the projects located on my MacBook and the VirtualBox guest mounts these instead. Cured all of my problems.

And to maybe spare you from digging further into it, this didn't just happen with TextMate. I tried other editors as well, some of them didn't even show a notice that the save didn't go through and just silently went on. Re-openend the file and all changes were gone.

At times it helped touching the file directly on the guest system (via touch or a text editor), but it wasn't a sure fix.

I know it's not a solution to the problem at hand, but maybe sheds some light. Pretty sure these are issues within the mounting process.


On Thu, Jun 16, 2016 at 11:09 PM, Carpii UK <carpii.uk@gmail.com> wrote:
I'm still trying to get to the bottom of this, but not making much progress 

Im starting to wonder if its possible a bundle I use could be involved somehow?

Heres a screenie of the JSHint bundle steps.... 

Is it possible TM could be piping the document to the bundle, before the atomic save step has fully completed? 

It still wouldn't explain why I sometimes see the issue on non JS files (such as .tm_properties), but its definitely gotten worse since moving from AFP to SMB, so it feels like there is some race condition involved somehow.

I've also tried Atom quite a bit over the past week, but was not able to reproduce any issues in that editor
I think I can rule out any issues with my SMB configuration, based on that. 

Thanks


On 5 June 2016 at 17:53, Carpii UK <carpii.uk@gmail.com> wrote:


On 5 June 2016 at 17:44, Allan Odgaard <mailinglist@textmate.org> wrote:
On 5 Jun 2016, at 18:32, Carpii UK wrote:

 I want you to run `mv` from your Mac so it goes through the Samba driver as well, i.e.:


Ok, I will do this next time it crops up
 
As for “write: Broken Pipe” I don’t see this error message in TextMate itself, so that’s a little puzzling. Was this the exact (and full) error message?

I believe I copy and pasted it from iTerm, but theres a small chance I just typed it in, so can't say 100%.
I will get some exact info on this too, next time I see it. 

Thanks
 



_______________________________________________
textmate mailing list
textmate@lists.macromates.com
http://lists.macromates.com/listinfo/textmate