Okay, so I just ran the script (after modifying the path to the file to match my system), and QS did not reactivate for me. I'm not sure why you are getting that behaviour. The best I can suggest is to quit QS, move ~/Library/Application Support/Quicksilver to the desktop, restart QS (this will reset it to defaults), add your custom action back in, and see if that solves the problem. If so, you can start re- adding things like Catalog.plist into the new App Support folder until you find the file that caused the problem. Whatever it was will need to be rebuilt using the QS gui.
On Jun 27, 7:33 pm, Sesquipedalian <[EMAIL PROTECTED]> wrote: > Disregard my previous post. It looked like there was a double-quote > character there, when it was actually two single-quote characters. > > On Jun 27, 7:30 pm, Sesquipedalian <[EMAIL PROTECTED]> wrote: > > > Is that exactly the script you are using? If so, I would guess it is > > not actually working, and QS might therefore be reactivating because > > the shell script is returning an error. > > > In specific, there should not be a " between echo and >>. > > > On Jun 27, 12:17 pm, David Saff <[EMAIL PROTECTED]> wrote: > > > > All, > > > > I've installed this as an AppleScript action: > > > > using terms from application "Quicksilver" > > > on process text projectName > > > set journal to "/Users/saff/Documents/Journal/journal.txt" > > > > do shell script "echo '' >> " & journal & "; echo > > > '#startProject " & > > > projectName & "' >> " & journal > > > end process text > > > end using terms from > > > > The script works perfectly, appending the text to the appropriate > > > file. However, after it finishes, Quicksilver pops back up, and I > > > have to Esc out to get back to work. How can I fix this? Thanks, > > > > David Saff
