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