[SOLVED] So I removed both the iTerm and Terminal plugins from QS and restarted it. Now when I try to call a python program that is in a catalog instead of being run it opens in TextEdit. I looked through the Actions and I found that there are four different Run commands, <Gear Icon> Run, <Applescript File Icon> Run, <Quicksilver Icon> Run, and <Terminal Icon> Run [...], plus others such as Run at Time, Run Javascript, etc.
Something changed on my system (probably my doing) and once I toggled the Run [...] option back on and made it the default for my iTerm scripts they now work properly. YAY!!!! Now my next question is what are each of the different Run actions for, I found my problem but I'd like to know a little more about it. Just like there are multiple Open File... actions along with Open ones. On May 11, 11:48 am, Brenden <[email protected]> wrote: > On May 3, 9:42 pm, Rob McBroom <[email protected]> wrote: > > > > > There’s an iTermplug-in. Ideally, this could be updated to know about those > > bookmarks and what to do with them. > > This would be the most ideal yes, unfortunately it didn't work with > how I was running things. > > > > > Because it uses the URL scheme, it’s limited to what can be in there. I > > don’t know of a way to specify commands to run in the URL. User and host > > seem to be all you can customize. > > > This isn’t ideal, but I have some common commands assigned to F-keys and > > the one I use the most is to run a command as soon as I log in. > > Unfortunately the customizations I have for each profile/bookmark iniTermis > more then just a connection command, it is also font and > color scheme. The main thing is that I see the broken functionality of > qslauch.py as being a regression, it worked before but now with the > newest version it behaves differently, that means something changed. > Unfortunately I'm not the greatest programmer and from my poking > around in the code I haven't been able to figure out what changed or > needs to be changed. > > > > > Again, this is a URL thing. Microsoft’s Remote Desktop client doesn’t > > register itself as being able to handle `rdp://` URLs (or anything else). > > CoRD does. I’ve resorted to saving RDP files and adding them to the > > catalog, but then I only have like two Windows boxes to worry about. The > > RDP files are just XML though, so you could make a script that generates > > them based on the contents of `.hosts` if you needed hundreds. > > Yeah making a bunch of .rdp files and having them cataloged by QS is > how I'm launching my RDP sessions. Wish I could do the same with vnc > sessions for JollyFast, it works so much nicer then the builtin vnc > client.
