guard-zeus 2.0.1.pre.alpha.pre.96 → 2.0.1

checksums.yaml

@@ -1,15 +1,7 @@
 ---
-!binary "U0hBMQ==":
-  metadata.gz: !binary |-
-    MjljYzNiZjA1NTc0YmY5NjJkMzkzMGVlNTY4NzQxYjVkODQ3N2VjYg==
-  data.tar.gz: !binary |-
-    OTBmNjYzYTk3NjU4ZGIzYjE2OGE2OWVlZGI2YjJkNTVhZWU4MTFhNA==
+SHA1:
+  metadata.gz: 1628512e33d06aa83de306e954a298a1411deb28
+  data.tar.gz: 461144205e85a5ca88406e52a5dcbf6db186bc87
 SHA512:
-  metadata.gz: !binary |-
-    NjIxZmYzMDc5YWVhM2E4Y2NkOTM3NTYyMzVjZmYxMTFkZDU3MzRjYjI3YzI5
-    Nzg5ZGNiNDYwZTcyNTJlOGEzYjhhOTE5ZjMwMjZkMTZjMzU4MDhkYmVkMGQ0
-    MDY2YTAwNTY3NjY4YWI1ODk3YzVhZTJkODI5MDhlZjAxZTkyMWY=
-  data.tar.gz: !binary |-
-    YzE1NjdlYTBhMmNhMTkyZmY4MGYxOTZjYzA4OTZkNTE4OTk1MmNkYzNmNDdm
-    ZDU5ZGRlNDlmZDZlNzMyZmZjYWM1NThiNjNmMWRkZDFlYWNjMDhhY2FjM2I1
-    YjQyYWMyMGQwMzgwOTA5MmMyZjAxODY3NDE4NzQzNzU5MmI3YzA=
+  metadata.gz: 997f4e431392fecb5322bd0370dc5891f78a77dc800a344a46e204c288441a193806f57731baf7eef292be93754d0c2b0e854d3e939b23381dbc62ff62ac728c
+  data.tar.gz: d5a39230867d2d5b04e5b1a676a9cdf41005f32926b6486a6b7124c4eb85dafabfaf11b8281d8e8e8f7ffea62ffdcb7d4229b9f31fad83d2ff7bd6e39cc6b62b

data/README.md

@@ -50,10 +50,7 @@ Available options:
 Known Issues
 ------------
 
-
-### Use with pry
-
-There is a known issue when using guard-zeus with pry, notably the zeus output appear on top of the pry console.
+There is a known issue when using guard-zues with pry, notably the zeus output appear on top of the pry console.
 
 The workaround is to add the `cli` setting in your `Guardfile`, e.g.
 
@@ -61,15 +58,6 @@ The workaround is to add the `cli` setting in your `Guardfile`, e.g.
 guard 'zeus', cli: '> /dev/null' do
 ```
 
-### Lingering zeus process
-
-If you have issues with `zeus` lingering around after exiting `guard`, you can
-add the following to the top of your `Guardfile`.
-
-```
-at_exit {exec('pkill -f zeus')}
-```
-
 Development
 -----------
 

data/lib/guard/zeus/runner.rb

@@ -85,31 +85,21 @@ module Guard
       end
 
       def spawn_zeus(cmd, options = '')
-        Compat::UI.debug "About to spawn zeus"
         @zeus_pid = fork do
           exec "#{cmd} #{options}"
         end
-        Compat::UI.debug "Zeus has PID #{@zeus_pid}"
       end
 
       def stop_zeus
-        Compat::UI.debug 'Stopping Zeus'
         return unless @zeus_pid
-        Compat::UI.debug 'Stopping Zeus using a PID'
 
-        Compat::UI.debug "Killing process #{@zeus_pid}"
         Process.kill(:INT, @zeus_pid)
-        Compat::UI.debug "Killed process #{@zeus_pid}"
 
         begin
-          Compat::UI.debug "Set process #{@zeus_pid} to wait"
           unless Process.waitpid(@zeus_pid, Process::WNOHANG)
-            Compat::UI.debug "Killing process #{@zeus_pid} after wait"
             Process.kill(:KILL, @zeus_pid)
-            Compat::UI.info "Killed process #{@zeus_pid} after wait"
           end
         rescue Errno::ECHILD
-          Compat::UI.debug "ECHILD path"
         end
 
         delete_sockfile if File.exist? sockfile

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: guard-zeus
 version: !ruby/object:Gem::Version
-  version: 2.0.1.pre.alpha.pre.96
+  version: 2.0.1
 platform: ruby
 authors:
 - jonathangreenberg
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2016-07-11 00:00:00.000000000 Z
+date: 2015-01-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: guard
@@ -92,18 +92,19 @@ require_paths:
 - lib
 required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ! '>='
+  - - '>='
     - !ruby/object:Gem::Version
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ! '>'
+  - - '>='
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.5
+rubygems_version: 2.4.1
 signing_key: 
 specification_version: 4
 summary: Pushes watched files to Zeus
 test_files: []
+has_rdoc: