I was seeing an issue where modifying PATH caused the Ruby plugin
tests to fail. I fixed that and while digging around fixed an issue
that would cause the tests to behave weirdly if run from any other
location.
This solves one of the issues noted in #687, but I haven't tried
running the new tests from that PR with these changes.
- "bash-it search term1 [term2]...."
- we are using existing 'bash-it show plugins|aliases|completions'
commands output, to search (with grep) for lines that match the
search terms, and then output the matches.
- wrote a simple unit test that for whatever reason fails on Travis,
so wrapped it in 'if "Darwin"'...
