That gave me some good things to look at. I've narrowed down the problem. Both the Terminal Module and Core Support provide an action named "Run [...]" which applies to unix executables. If I have the Terminal Module installed (active/selected or not), this behavior exists; if I uninstall the Terminal Module, I get back the old behavior. Unfortunately, the simple existence of the action in the Terminal Module is sufficient to block the Core Support action; unselecting the action while installed makes neither be available.
Is it expected that modules be able to override the behavior of built- in actions? Did who "wins" a conflict change between releases? For now I've uninstalled the Terminal Module, since this sequence is the single most common thing I do with Quicksilver. It would be nice to get back the ones Terminal Module provides, though; the "Run Command in Shell" action in particular is quite useful. Anthony
