On 5 Aug 2016, at 12:09, jwmann wrote:
I tried adding &>/dev/null after the last command but didn't seem to
affect
anything.
Perhaps I'm just doing it wrong? I'm no expert at shell scripting.
I reviewed [some documentation that I wrote][devref] (but obviously
don’t remember) and the interface won’t pop back up if nothing is
returned, so that might actually work if you can silence the script.
I’m not sure which action you’re using to run the script, but I just
tested
cat ⇥ Run Command in Shell
and
ls ⇥ Run Command in Shell
And the interface only re-appeared for the second one (because it had
output). So if silencing the script doesn’t work with the current
action, try creating the trigger as
/full/path/to/script.sh ⇥ Run Command in Shell
To see if the script will be silent or not, I’d just run it directly
in Terminal and see what pops out. That might help narrow down the
source (though it almost has to be one of the last two commands).
[devref]:
http://projects.skurfer.com/QuicksilverPlug-inReference.mdown#qsactions
--
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.
