Just so you know:
Today I noticed TM didn't send the file back to Fugu anymore on save. (It can be weird when you think you saved files when, in fact, you didn't!)
After reinstalling TM, rebooting, repairing permission, etc., I remembered I had enabled "atomic save" earlier. This was the problem, everything back to normal when it's unchecked.
I don't know if the problem is in Fugu or TM. Shouldn't TM falls back to normal writes?
Anyway, here is a log entry in case it helps:
------------- 2005-02-09 03:51:15.255 TextMate[555] initWithOptions: { auxiliaryFileInfo = { customPath = "sftp://fatal@10.0.0.115/temp/test.txt"; fsref = <NSAppleEventDescriptor: fsrf($FF9C80000013A3280013A3270000000000000000000000000000000000000000… $) 2005-02-09 03:51:19.086 Fugu[528] coerceToDescriptorType typeFileURL failed. 2005-02-09 03:51:20.822 Fugu[528] Couldn't coerce descriptor to typeFSS --------------
I know, it's late here. Must sleep! ;)
-- Fred
According to Fred B.:
After reinstalling TM, rebooting, repairing permission, etc., I remembered I had enabled "atomic save" earlier. This was the problem, everything back to normal when it's unchecked.
I guess that answers my question about Fugu :(
On Feb 9, 2005, at 4:02, Fred B. wrote:
After reinstalling TM, rebooting, repairing permission, etc., I remembered I had enabled "atomic save" earlier. This was the problem, everything back to normal when it's unchecked.
I don't know if the problem is in Fugu or TM. Shouldn't TM falls back to normal writes?
TM does fall back to normal writes if it can't do it atomically. But I think the problem is that the FSRef is pointing to nil after the atomic save, and this is likely TM's fault -- I'll look into it.
-
Allan Odgaard -
Fred B. -
Ollivier Robert