Thank you both for responding. When I'm back in the office on Monday, I will backup, repair permissions and report back. It may be something funky like that (but my gut tells me otherwise).
@Jon: Unfortunately, your applescript caused the same issue. I even tried making the contents of the script one line: -- test Just a comment. And I still got the behavior. It seems like the presence of ANY Applescript causes the problem. I also checked to ensure I can actually execute Applescript at all, running scripts I have in iTunes and Finder, and there was no issue. Also, the three "set...to null" lines seemed to be the only way I could find to prevent Quicksilver from reappearing after executing my script. I just want it to add the line to the text file, but after executing the script, Quicksilver would reappear, expecting me to perform an action on the text file itself. I don't want to get off topic, but if there's a better way to do it, I'm all ears. @Howard: Good thought, but no, there seems to be only one Quicksilver on my system. On Dec 7, 8:42 am, Howard Melman <[EMAIL PROTECTED]> wrote: > On just a random thought and seeing the (correct) line: > > > using terms from application "Quicksilver" > > is it possible you have two different Quicksilver's installed? > > Howard
