Skip to content

Guard 2.10.3 exits when Guardfile is changed.

Jump to bottom Edit New page
e2 edited this page Dec 11, 2014 · 2 revisions

Description

If you are watching the directory with the Guardfile (not recommended), Guard will exit so you can restart it manually.

History

This used to happen automatically, but the feature was dropped because it was unreasonably expensive to maintain. On top of that, the directories statement makes detecting the change trickier.

For details and a workaround go here: https://github.com/guard/guard/issues/688

Second problem

This warning also means you are watching the whole project directory.

This is not recommended and can cause lots of strange issues.

Solution

What you should do instead (if you can) is use the directories statement in the Guardfile or use the '-w` option to listen only to meaningful directories.

You will also want to move the top-level files you want to listen to a different directory (e.g. config) watch that dir instead (see directories), and symlink them back.

For details see: https://github.com/guard/guard/wiki/Optimizing-for-large-projects

This wiki and the Guard README document contains a lot of information, please take your time and read these instructions carefully.

If you run into any trouble, you may start by understanding how Guard works.

We provide detailed changes for each Guard release.

Be sure to read the CONTRIBUTING guidelines before reporting a new Guard issue or open a pull request.

If you have any questions about the Guard usage or want to share some information with the Guard community, please go to one of the following places:

Intro

Installation

Getting Started

Troubleshooting

Advanced use of Guard

Cookbooks

Development

Clone this wiki locally