Reload instead of run_all #8

Merged
merged 1 commit into from Oct 18, 2011

Conversation

Projects
None yet
2 participants
@tehpeh
Contributor

tehpeh commented Oct 17, 2011

Hi John,

This is what I meant regarding issue 6.

I've replaced run_all with reload so when a user hits return, nothing happens, but when they hit r+return the rails server restarts. This means you can use return to just run all tests, and r+return to restart rails, spork etc...

Any watched files will restart rails when touched, the same way it happens now.

What do you think? Does that work for you?

Tim Preston
Swapped run_all for reload.
This means hitting return will not reload rails server,
instead 'r' or 'reload' must be issued.

johnbintz added a commit that referenced this pull request Oct 18, 2011

@johnbintz johnbintz merged commit 63c648c into johnbintz:master Oct 18, 2011

@johnbintz

This comment has been minimized.

Show comment
Hide comment
@johnbintz

johnbintz Oct 18, 2011

Owner

So I guess you're stacking your Rails runner and tests in one group/guard, then. I'll take a cue from guard-spork and support the same reload behavior, then. Consider your patch merged. :) Thanks for contributing!

Owner

johnbintz commented Oct 18, 2011

So I guess you're stacking your Rails runner and tests in one group/guard, then. I'll take a cue from guard-spork and support the same reload behavior, then. Consider your patch merged. :) Thanks for contributing!

@tehpeh

This comment has been minimized.

Show comment
Hide comment
@tehpeh

tehpeh Oct 18, 2011

Contributor

Ok now I see. I was using different groups for a while, but now just run everything together. I run rails in daemon mode and tail the logs when I need to see what's going on.

Contributor

tehpeh commented Oct 18, 2011

Ok now I see. I was using different groups for a while, but now just run everything together. I run rails in daemon mode and tail the logs when I need to see what's going on.

ranmocy referenced this pull request in ranmocy/guard-rails May 14, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment