On Feb 26, 2013, at 5:13 PM, 1.61803 <[email protected]> wrote: > So, to disable a trigger on a per process per open Terminal session basis is > not feasible at all?
It might be possible using AppleScript to ask the frontmost Terminal window what it’s process is, but like I said, if a process is running inside screen or an SSH session, Terminal will just report “screen” or “ssh”. You’d also need to ask iTerm, in case the process is running there. And assuming it even worked, this AppleScript rat’s nest would have to be baked into the global trigger code. The final problem is that QS would have no way to know when the “active” process changed. OS X sends out a notification every time you switch applications, which is how Quicksilver is able to hide itself, enable/disable triggers, etc. There are no notifications for switching between tabs and windows in Terminal, or for starting new processes in an existing one. So, no. > I think this could be of interest to those who work a lot in Terminal and > have many potentially overlapping triggers/shortcuts. It would be nice, but I think just disabling certain triggers in Terminal probably covers 90% of these cases. And there are alternatives. You could assign Mouse or (soon) Gesture triggers for things that conflict with Vim shortcuts. Or you could just do some things the “hard” way (which is never really that hard in Quicksilver). -- Rob McBroom <http://www.skurfer.com/> -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
