{"shas":[["f3cbfab956c1f62cb5b6ba2ff8eee6b0d1ac23d7","207f226b989ff467014a01de18813126b838b2f1@web.de","Invoke rspec directly; notify user of problems with running the specs\n\nInstead of shelling out to the rspec executable, we require 'rspec/core'\nand start the runner directly. This has the advantage that we can catch\nexceptions that are raised while trying to run the specs and notify the\nuser that something is wrong.\n\nFor example, previously, when a syntax error in the specs prevented\nrspec from running, the user had to check the terminal for error\nmessages instead of being notified via growl/libnotify.\n\nNOTE: This breaks the Guard::RSpec::Runner specs and needs further\ntesting, especially under rspec 1, where it might not run at all. There\nalso is dead code now, #rspec_command for example, which will have to\nbe cleaned up. I haven't done this yet, because I'm not quite sure what\nexactly can be deleted.","Johannes Holzfuß"]],"repo":"DataWraith/guard-rspec","actor":"DataWraith","ref":"refs/heads/master","size":1,"head":"f3cbfab956c1f62cb5b6ba2ff8eee6b0d1ac23d7","actor_gravatar":"984f455451d7f0f2c1420af2f81957b8","push_id":30814300}