Yeah, QS should send SIGKILL, not SIGQUIT. I've submitted a pull request here: Use SIGKILL instead of SIGQUIT to Force Quit <https://github.com/quicksilver/ProcessManipulationPlugIn-qsplugin/pull/4>
On Wednesday, 2 March 2016 08:53:49 UTC-7, Rob McBroom wrote: > > On 2 Mar 2016, at 9:33, 1.61803 wrote: > > > I thought the parentheses referred to the signal sent, which is > > actually > > QUIT, not KILL or even the default TERM. > > It does seem to be sending QUIT instead of KILL, which I agree is weird. > I’ve never worked on that plug-in and don’t know the thinking behind > that. > > You can see what it’s doing here: > > > https://github.com/quicksilver/ProcessManipulationPlugIn-qsplugin/blob/master/QSProcessManipulationPlugInAction.m > > > > What does "Quit" action actually do? > > It uses Apple Events to tell the application to quit. I assume it’s > equivalent to ⌘Q in the app. > > (If you want to look, that action is implemented in Quicksilver itself > inside the Core Support plug-in.) > > -- > 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 https://groups.google.com/group/blacktree-quicksilver. For more options, visit https://groups.google.com/d/optout.
