What you see is the Guard Guard, which uses Pry . Usually the prompt looks a little different, so I assume that you have a ~/.pryrc with some configuration. In Guard Guard 1.5.3, released yesterday, Guard ignores ~/.pryrc and evaluates only ~/.guardrc for the Pry configuration, so the regular Pry configuration is separate from the Guard Pry interactive device.
When you see this invitation, it means that the Guard is waiting and there is nothing to do. Now you can start working, and Guard will automatically start testing your application with minitest according to your file changes and observer configuration, or you can manually initiate an action.
You can get a list of available actions with help guard . Some commands are created depending on your plugins and Guard groups in your Guardfile . Here is an example of one of my projects:
$ bundle exec guard 09:58:14 - INFO - Guard uses GNTP to send notifications. 09:58:14 - INFO - Guard is now watching at '/Users/michi/Repositories/extranett' 09:58:15 - INFO - Guard::Jasmine starts Unicorn test server on port 8888 in development environment. 09:58:17 - INFO - Waiting for Jasmine test runner at http://dnndev.me:8888/jasmine 09:58:23 - INFO - Run all Jasmine suites 09:58:23 - INFO - Run Jasmine suite at http://dnndev.me:8888/jasmine 09:58:41 - INFO - Finished in 8.853 seconds 09:58:41 - INFO - 896 specs, 0 failures 09:58:41 - INFO - Done. 09:58:41 - INFO - Guard::RSpec is running 09:58:41 - INFO - LiveReload 1.6 is waiting for a browser to connect. [1] guard(main)> help guard Guard all Run all plugins. backend Run all backend change Trigger a file change. coffeescript Run all coffeescript frontend Run all frontend jasmine Run all jasmine livereload Run all livereload notification Toggles the notifications. pause Toggles the file listener. reload Reload all plugins. rspec Run all rspec show Show all Guard plugins. [2] guard(main)> exit 09:59:39 - INFO - Guard::Jasmine stops server. 09:59:39 - INFO - Bye bye...
Netzpirat
source share