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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. checksums.yaml +5 -13
  2. data/README.md +1 -13
  3. data/lib/guard/zeus/runner.rb +0 -10
  4. metadata +7 -6
checksums.yaml CHANGED
@@ -1,15 +1,7 @@
1
1
  ---
2
- !binary "U0hBMQ==":
3
- metadata.gz: !binary |-
4
- MjljYzNiZjA1NTc0YmY5NjJkMzkzMGVlNTY4NzQxYjVkODQ3N2VjYg==
5
- data.tar.gz: !binary |-
6
- OTBmNjYzYTk3NjU4ZGIzYjE2OGE2OWVlZGI2YjJkNTVhZWU4MTFhNA==
2
+ SHA1:
3
+ metadata.gz: 1628512e33d06aa83de306e954a298a1411deb28
4
+ data.tar.gz: 461144205e85a5ca88406e52a5dcbf6db186bc87
7
5
  SHA512:
8
- metadata.gz: !binary |-
9
- NjIxZmYzMDc5YWVhM2E4Y2NkOTM3NTYyMzVjZmYxMTFkZDU3MzRjYjI3YzI5
10
- Nzg5ZGNiNDYwZTcyNTJlOGEzYjhhOTE5ZjMwMjZkMTZjMzU4MDhkYmVkMGQ0
11
- MDY2YTAwNTY3NjY4YWI1ODk3YzVhZTJkODI5MDhlZjAxZTkyMWY=
12
- data.tar.gz: !binary |-
13
- YzE1NjdlYTBhMmNhMTkyZmY4MGYxOTZjYzA4OTZkNTE4OTk1MmNkYzNmNDdm
14
- ZDU5ZGRlNDlmZDZlNzMyZmZjYWM1NThiNjNmMWRkZDFlYWNjMDhhY2FjM2I1
15
- YjQyYWMyMGQwMzgwOTA5MmMyZjAxODY3NDE4NzQzNzU5MmI3YzA=
6
+ metadata.gz: 997f4e431392fecb5322bd0370dc5891f78a77dc800a344a46e204c288441a193806f57731baf7eef292be93754d0c2b0e854d3e939b23381dbc62ff62ac728c
7
+ data.tar.gz: d5a39230867d2d5b04e5b1a676a9cdf41005f32926b6486a6b7124c4eb85dafabfaf11b8281d8e8e8f7ffea62ffdcb7d4229b9f31fad83d2ff7bd6e39cc6b62b
data/README.md CHANGED
@@ -50,10 +50,7 @@ Available options:
50
50
  Known Issues
51
51
  ------------
52
52
 
53
-
54
- ### Use with pry
55
-
56
- There is a known issue when using guard-zeus with pry, notably the zeus output appear on top of the pry console.
53
+ There is a known issue when using guard-zues with pry, notably the zeus output appear on top of the pry console.
57
54
 
58
55
  The workaround is to add the `cli` setting in your `Guardfile`, e.g.
59
56
 
@@ -61,15 +58,6 @@ The workaround is to add the `cli` setting in your `Guardfile`, e.g.
61
58
  guard 'zeus', cli: '> /dev/null' do
62
59
  ```
63
60
 
64
- ### Lingering zeus process
65
-
66
- If you have issues with `zeus` lingering around after exiting `guard`, you can
67
- add the following to the top of your `Guardfile`.
68
-
69
- ```
70
- at_exit {exec('pkill -f zeus')}
71
- ```
72
-
73
61
  Development
74
62
  -----------
75
63
 
@@ -85,31 +85,21 @@ module Guard
85
85
  end
86
86
 
87
87
  def spawn_zeus(cmd, options = '')
88
- Compat::UI.debug "About to spawn zeus"
89
88
  @zeus_pid = fork do
90
89
  exec "#{cmd} #{options}"
91
90
  end
92
- Compat::UI.debug "Zeus has PID #{@zeus_pid}"
93
91
  end
94
92
 
95
93
  def stop_zeus
96
- Compat::UI.debug 'Stopping Zeus'
97
94
  return unless @zeus_pid
98
- Compat::UI.debug 'Stopping Zeus using a PID'
99
95
 
100
- Compat::UI.debug "Killing process #{@zeus_pid}"
101
96
  Process.kill(:INT, @zeus_pid)
102
- Compat::UI.debug "Killed process #{@zeus_pid}"
103
97
 
104
98
  begin
105
- Compat::UI.debug "Set process #{@zeus_pid} to wait"
106
99
  unless Process.waitpid(@zeus_pid, Process::WNOHANG)
107
- Compat::UI.debug "Killing process #{@zeus_pid} after wait"
108
100
  Process.kill(:KILL, @zeus_pid)
109
- Compat::UI.info "Killed process #{@zeus_pid} after wait"
110
101
  end
111
102
  rescue Errno::ECHILD
112
- Compat::UI.debug "ECHILD path"
113
103
  end
114
104
 
115
105
  delete_sockfile if File.exist? sockfile
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: guard-zeus
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.0.1.pre.alpha.pre.96
4
+ version: 2.0.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - jonathangreenberg
@@ -10,7 +10,7 @@ authors:
10
10
  autorequire:
11
11
  bindir: bin
12
12
  cert_chain: []
13
- date: 2016-07-11 00:00:00.000000000 Z
13
+ date: 2015-01-13 00:00:00.000000000 Z
14
14
  dependencies:
15
15
  - !ruby/object:Gem::Dependency
16
16
  name: guard
@@ -92,18 +92,19 @@ require_paths:
92
92
  - lib
93
93
  required_ruby_version: !ruby/object:Gem::Requirement
94
94
  requirements:
95
- - - ! '>='
95
+ - - '>='
96
96
  - !ruby/object:Gem::Version
97
97
  version: '0'
98
98
  required_rubygems_version: !ruby/object:Gem::Requirement
99
99
  requirements:
100
- - - ! '>'
100
+ - - '>='
101
101
  - !ruby/object:Gem::Version
102
- version: 1.3.1
102
+ version: '0'
103
103
  requirements: []
104
104
  rubyforge_project:
105
- rubygems_version: 2.4.5
105
+ rubygems_version: 2.4.1
106
106
  signing_key:
107
107
  specification_version: 4
108
108
  summary: Pushes watched files to Zeus
109
109
  test_files: []
110
+ has_rdoc: