On 20 juin 05, at 06:12, Tim Martens wrote:

On Jun 19, 2005, at 4:30 AM, Allan Odgaard wrote:

The beeps are from TextMate, and there to indicate that there was “error sending back modified file”. However, the error is with the reply event sent by Transmit.

What version of TextMate and Transmit are you using?

1.1b12 and 3.2

I'm not sure what the “index (0) beyond bounds” is from. Does this always appear before the former error message?

Same here, opening and saving files via Transmit does beep and throw an error but it is working.

I didn't noticed it before because the sound used by Transmit to notice a completed transfer is the Alert sound (good example of why this is a bad idea!).

When I open a file in TM from Transmit:

2005-06-21 18:44:16.118 TextMate[2243] Exception raised during posting of notification. Ignored. exception: *** -[NSCFArray objectAtIndex:]: index (0) beyond bounds (0)

2005-06-21 18:44:16.351 TextMate[2243] Exception raised during posting of notification. Ignored. exception: *** -[NSCFArray objectAtIndex:]: index (0) beyond bounds (0)

2005-06-21 18:44:16.355 TextMate[2243] Exception raised during posting of notification. Ignored. exception: *** -[NSCFArray objectAtIndex:]: index (0) beyond bounds (0)

When I save it:

2005-06-21 18:45:16.766 TextMate[2243] *** error sending back modified file -1701 (/Users/fatal/Library/Caches/TemporaryItems/Transmit/.tmp_uftezy/README)

2005-06-21 18:45:16.779 TextMate[2243] Exception raised during posting of notification. Ignored. exception: *** -[NSCFArray objectAtIndex:]: index (0) beyond bounds (0)

2005-06-21 18:45:16.951 TextMate[2243] Exception raised during posting of notification. Ignored. exception: *** -[NSCFArray objectAtIndex:]: index (0) beyond bounds (0)

2005-06-21 18:45:16.955 TextMate[2243] Exception raised during posting of notification. Ignored. exception: *** -[NSCFArray objectAtIndex:]: index (0) beyond bounds (0)

Nothing in the console doing the same with TextWrangler.

Fred