Yeah, seems to be deeper down. I thought when I last experienced this that I was able to just use another editor. That's why I thought that it's an TM issue. Just checked again and that's not the case anymore. Every editor gives an error on save. Even git reports that the resource is busy.

Funny thing is, that this seems to happen with random files. Some I can edit, some I can't.

I'll see if I can find an answer related to mounted shares then.

Thanks for your reply!

On Thu, Jul 3, 2014 at 4:59 PM, Carpii UK carpii.uk@gmail.com wrote:

I have this problem occasionally on an AFP share.

Check the file permissions, and see if you can save with a different editor as a test.

In my case, I believe it is due to a network link to my AFP server going down temporarily, and then even restarting TM doesn't always fix it. Restarting the AFP service itself does fix it, however. I dont believe its a TM issue, but perhaps an issue at the OS/AFP level

On 1 July 2014 16:29, Matthias mawe@typeofundefined.com wrote:

...

I have a Windows share mounted via smb:// and TextMate won't save any file I edit there. The error message is "Atomic save: Resource busy".

It's Windows 7 running inside a virtual machine (VirtualBox) and Textmate is at 2.0-alpha.9547.

Is there anything I can do about this?

Regards, Matthias

---

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

---

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