John Bintz
776361d038
add a sleep to the interactor thread, because it's healthy to take a break every once in a while
2011-09-30 11:22:35 -04:00
Michael Kessler
a1f37f60d6
Re-evaluate the Guardfile before reload all Guards ( Fixes #141 ).
2011-09-24 12:58:27 +02:00
Michael Kessler
072d5404ee
Merge pull request #137 from hron/guard
...
---
It seems like the new interactor eats input from $stdin even while it is locked. This disallow using tools like ruby-debug or pry in specs or cucumber.
The fix just kills the interactor when it is locked and runs it again when ulocked.
Conflicts:
lib/guard/interactor.rb
2011-09-21 00:34:11 +02:00
Aleksei Gusev
8c6a30795a
Change Guard::Interactor#lock and #unlock methods so they will lock interactor
...
in the right thread and free $stdin [closes #137 ].
2011-09-20 21:54:21 +03:00
Michael Kessler
ad6fe6f69b
Yardoc for the interactor.
2011-09-20 13:10:16 +02:00
Aleksei Gusev
443f57efce
Fix interacting with tools like ruby-debug.
...
It seems like the new interactor eats input from $stdin even while it locked.
This disallow using tools like 'ruby-debug' or 'pry' in specs or cucumber.
The fix just kills the interactor when it is locked and runs it again when
ulocked.
2011-09-19 23:27:05 +03:00
Thibaud Guillaume-Gentil
c4ddb29fc6
Work on specs
2011-09-01 23:24:45 +02:00
Thibaud Guillaume-Gentil
3717179591
Refactor new interactor/listener mechanic now it's
...
look pretty.
Specs still need some love :)
2011-08-30 21:13:51 +02:00
Thibaud Guillaume-Gentil
e752dbe1c1
Maybe first working version (but still a work in progress)
2011-08-29 21:25:58 +02:00
Thibaud Guillaume-Gentil
af408ceb65
Add thread in guard interactor
2011-08-17 10:07:30 +02:00
Thibaud Guillaume-Gentil
573ddf9d9d
First trial to remove Posix Signals interaction
2011-08-13 16:43:32 +02:00
Rémy Coutable
b34cd1acfb
Based on @ttilley explanation in https://github.com/thibaudgg/rb-fsevent/issues/17 , signal handlers registration should happen before any subprocess creation (fsevent_watch for instance) to be properly catches by the subprocess.
...
Note that in the case when guard is run via bundler, this –quoting @ttilley– "would make this an unsolvable problem" (isn't it dramatic?! ;)).
2011-07-30 23:58:53 +02:00
Thibaud Guillaume-Gentil
e0ca761a25
Removed useless \n when saying 'Bye bye...'
2011-05-13 22:05:58 +02:00
Thibaud Guillaume-Gentil
5352528530
Merge branch 'master' of https://github.com/stereobooster/guard into stereobooster-master
...
Conflicts:
lib/guard/interactor.rb
2011-05-06 23:35:09 +02:00
Thibaud Guillaume-Gentil
fa44ef31bc
Moved stop "\n"
2011-05-06 22:58:18 +02:00
Nick Sieger
70c15a7c94
Extract code from signal handlers into methods
...
This will allow building other mechanisms to interact with Guard, for
example on JRuby, where signal handling tends to be unreliable.
2011-05-06 12:45:47 -05:00
slavic
cbe2cb353c
fix issue #27
2011-04-24 20:21:39 +03:00
Thibaud Guillaume-Gentil
2fc6745837
Merge branch 'master' of github.com:guard/guard
...
Conflicts:
lib/guard.rb
lib/guard/interactor.rb
spec/guard_spec.rb
2010-11-30 21:23:53 +01:00
Thibaud Guillaume-Gentil
53a79691a5
Kept listener running in thread even when guards plugin are also running.
2010-11-30 21:15:03 +01:00
Rémy Coutable
7f39a55fdf
Use 'guard' instead of 'g', use parenthesis and don't explicitly return when not necessary
2010-11-26 00:58:36 +01:00
Olivier Amblet
cb8b845eb6
A bad guard do not threaten the whole process.
...
Every guard task are now executed through
supervised_task method.
If a guard failed to achieve its task(raise error)
a message is logged and the guard is fired.
The stop method now always quit the application
at the end.
Specs added. The documentation specify that if a
throw an exception, it will be dismissed.
2010-10-27 15:18:00 +02:00
Thibaud Guillaume-Gentil
c347c2c7e0
Added 1.8.6 compatibility
...
Closes #2 .
2010-10-18 21:45:31 +02:00
Thibaud Guillaume-Gentil
8b5ecd9a8a
Added debug start option
2010-10-10 12:38:25 +02:00
Thibaud Guillaume-Gentil
4d3744ff43
Initial commit
2010-10-03 23:00:33 +02:00
