I made a github issue. https://github.com/quicksilver/Quicksilver/issues/1034
On Thursday, August 2, 2012 6:14:07 PM UTC-4, umop wrote: > > Agreed. > > And thank you. The Applescript solution worked! > > On Wednesday, August 1, 2012 11:43:37 AM UTC-7, mason k wrote: >> >> By the way, I think there might have been an oversite in the removal of >> Run [...] (Run with arguments). There is now no way to trigger shell >> commands without editing a plist file, which is a common and useful thing >> to want to do with quicksilver. I recommend that Run [..] (Run in Terminal) >> always show the third pane. If people don't want to enter arguments, then >> they simply won't, and everything will work. >> >> On Tuesday, July 31, 2012 10:25:56 PM UTC-4, mason k wrote: >>> >>> You can tab into Run in Terminal [...] and enter arguments in the third >>> pane. If you want to create triggers, take a look at Patrick's answer to my >>> similar question >>> https://groups.google.com/forum/?fromgroups#!topic/blacktree-quicksilver/o4oZiwhIQcc >>> . >>> >>> On Tuesday, July 31, 2012 3:04:17 PM UTC-4, umop wrote: >>>> >>>> I am running the latest Quicksilver, and the Run [...] (Run with >>>> arguments) action does not appear. Run (no [...]) appears, and Run in >>>> Terminal [...] appears, but no Run [...] as it does on my other >>>> machines with QS (older and newer versions) installed. I checked my ~/ >>>> Library/Application Support/Quicksilver/Actions directory, and there >>>> is no Core Support plugin found in there. Any ideas? >>>> >>>> Thanks! >>>> >>> -- You received this message because you are subscribed to the Google Groups "Quicksilver" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/blacktree-quicksilver?hl=en.
