Actually, I just noticed that the latest Terminal plugin update provides two copies of the Run a Text Command in Terminal action. One is the correct one, and one is a duplicate that is causing this problem. The broken version appears high up in the Actions list. Just disable that one, and all will be well until the fixed version of the plugin goes out.
If you want to follow the official bug report for this, you can do so at https://github.com/quicksilver/Quicksilver/issues/1980 On Monday, November 3, 2014 9:04:02 PM UTC-7, Jon Stovell wrote: > > If you installed the recent update to the Terminal plugin, your > preferences may have adjusted the Run Text Command in Terminal action so > that it appears for applications. I think this is a bug, and I expect the > developers will fix it soon. In the meantime, you can just drag the Run > text Command in Terminal action down to a lower priority in the Actions > list in the main tab of QS's preferences. > > On Monday, November 3, 2014 3:20:33 PM UTC-7, dingster wrote: >> >> Hello, >> >> I just upgraded my OS to Yosemite and overtime I tried to open an app >> with QS I get a terminal window stating "command not found". Does anyone >> know what the issue is and how to resolve this? >> >> Thanks in advance. >> >> - Daniel >> > -- You received this message because you are subscribed to the Google Groups "Quicksilver" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/blacktree-quicksilver. For more options, visit https://groups.google.com/d/optout.
