Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Apple Events Debugging: CAVEAT' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Apple Events Debugging: CAVEAT
Authored by: jimr on Jul 03, '06 02:33:04AM
This is an old hint, but still works.

At sometime I certainly installed the environment.plist file in my system, watched for Apple events, and promptly forgot about how it was done. Possibly, It was installed by an app called AE Monitor.

There are a few caveats.. first, it fills up your console.log with this debugging data as well, and several times I was able to use it, so I never got too worried about that...

Second, and this has been a major problem, as it took a very long time to come to a solution, it seems that AE debugging interferes with BBEdit's sftp logins. Though, every other application supporting the sftp protocol, and the command line seem to work just fine.

Now I had never seen this reported anywhere, and for some time I supposed it was a bug in either My Operating System (heavily tweaked), or in some other faulty configuration.

I searched EVERYWHERE for answers to the sftp problem. but have had no luck during the year or more that the problem has been following me around.

And, when I say following me, I mean, that I finally determined that BBEdit sftp was working just fine on any other account in my room and on *gasp* my machine...

It wasn't a super serious fault in my favorite text editor, especially as the excellent CYBERDUCK sftp client will work seamlessly with the text editor of choice...

It was just at the lower threshold of PITA... and so I let it slide for quite a long time, though, it was a bit frustrating.

So today, midst some system maintenance and upgrades , I decided to more carefully examine some of the differences between the normal login account and the spare account.

I noted that the AEDebugging was not global, and as I was looking for a non-global setting, I started to investigate in earnest.

Google soon led me to this hint as I was looking for a source of AE2000 debugger statements in my logs... so, here is one way to put them there..

And I surely found the ~/.MACOSX directory absent in the spare user account where things work perfectly, yet have none of my special customization ;-)

upon removal, and a restart... (Well.... the newest QT installer wanted that...)

The BBEdit sftp no longer fails upon activation and of course the logs will be free of AE property list declarations...
As you can read the hint, it's easy to turn back on... but it seems, you never know when some app, even the well written ones, will fail due to some customization.

Finally for the search engines... this BBEdit failure during sftp login is solved by disabling AEDebug

Though, as a developer, one may actually require AEDebugging and BBEdit sftp simultaneously ;-)


[ Reply to This | # ]