guard/listen — Issue #11: Innacurate documentation or bug?
Author: rurounijones
Created: 2012-03-07 09:47:44+00:00
State: open

Documentation such as the following from the README

```
listener = Listen.to('dir/path/to/listen')
listener.start # enter the run loop
listener.pause # stop listening changes
listener.paused? => true
listener.unpause
listener.stop
```

Does not work in the sense that listener.start blocks so pause, unpause etc. will never actually get executed.

From the messing around that I have done it seems that listener.start always needs to be wrapped in a Thread.new but looking at the source code threads are used internally so I am not sure why listener.start is blocking in the first place.

Is this a bug in that .start should not block? Or is it a case that my interpretation of the documentation is inaccurate.

Attempted on Ubuntu 10.04 64-Bit (ext3) with MRI 1.9.3 and Jruby 1.6.7