Thanks for the explanation, Jon. This is what I found after some more testing.
echo $0 ⇥ Run Command in Shell returns /bin/sh On Tuesday, April 2, 2013 5:12:10 AM UTC+2, Jon Stovell wrote: > > In OS X, the sh executable is really bash, but bash run in a special mode > by calling it as sh. > The reason none of your bash aliases work, 1.61803, is explained in this > section from the bash man page: > If bash is invoked with the name sh, it tries to mimic the > startup > behavior of historical versions of sh as closely as possible, > while > conforming to the POSIX standard as well. > This behaviour is not documented in the plugin. Run Command in Shell is a misnomer. It could be Run Command in shell or Run Command in Shell(sh). Nowadays this action could run in $SHELL or whatever executable path the user may input. @Rob, is it hardcoded? And omt, non-default commands (except for one) run in sh but stderr is not handled by QS and logs _Quicksilver[43757]: Task failed._ Should I file a bug? I'll keep testing and post results if I find something useful. -- 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.
