guard-zeus 2.0.1.pre.alpha.pre.94 → 2.0.1.pre.alpha.pre.96
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.
- checksums.yaml +8 -8
- data/README.md +12 -0
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,15 +1,15 @@
|
|
|
1
1
|
---
|
|
2
2
|
!binary "U0hBMQ==":
|
|
3
3
|
metadata.gz: !binary |-
|
|
4
|
-
|
|
4
|
+
MjljYzNiZjA1NTc0YmY5NjJkMzkzMGVlNTY4NzQxYjVkODQ3N2VjYg==
|
|
5
5
|
data.tar.gz: !binary |-
|
|
6
|
-
|
|
6
|
+
OTBmNjYzYTk3NjU4ZGIzYjE2OGE2OWVlZGI2YjJkNTVhZWU4MTFhNA==
|
|
7
7
|
SHA512:
|
|
8
8
|
metadata.gz: !binary |-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
9
|
+
NjIxZmYzMDc5YWVhM2E4Y2NkOTM3NTYyMzVjZmYxMTFkZDU3MzRjYjI3YzI5
|
|
10
|
+
Nzg5ZGNiNDYwZTcyNTJlOGEzYjhhOTE5ZjMwMjZkMTZjMzU4MDhkYmVkMGQ0
|
|
11
|
+
MDY2YTAwNTY3NjY4YWI1ODk3YzVhZTJkODI5MDhlZjAxZTkyMWY=
|
|
12
12
|
data.tar.gz: !binary |-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
13
|
+
YzE1NjdlYTBhMmNhMTkyZmY4MGYxOTZjYzA4OTZkNTE4OTk1MmNkYzNmNDdm
|
|
14
|
+
ZDU5ZGRlNDlmZDZlNzMyZmZjYWM1NThiNjNmMWRkZDFlYWNjMDhhY2FjM2I1
|
|
15
|
+
YjQyYWMyMGQwMzgwOTA5MmMyZjAxODY3NDE4NzQzNzU5MmI3YzA=
|
data/README.md
CHANGED
|
@@ -50,6 +50,9 @@ Available options:
|
|
|
50
50
|
Known Issues
|
|
51
51
|
------------
|
|
52
52
|
|
|
53
|
+
|
|
54
|
+
### Use with pry
|
|
55
|
+
|
|
53
56
|
There is a known issue when using guard-zeus with pry, notably the zeus output appear on top of the pry console.
|
|
54
57
|
|
|
55
58
|
The workaround is to add the `cli` setting in your `Guardfile`, e.g.
|
|
@@ -58,6 +61,15 @@ The workaround is to add the `cli` setting in your `Guardfile`, e.g.
|
|
|
58
61
|
guard 'zeus', cli: '> /dev/null' do
|
|
59
62
|
```
|
|
60
63
|
|
|
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
|
+
|
|
61
73
|
Development
|
|
62
74
|
-----------
|
|
63
75
|
|
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.
|
|
4
|
+
version: 2.0.1.pre.alpha.pre.96
|
|
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:
|
|
13
|
+
date: 2016-07-11 00:00:00.000000000 Z
|
|
14
14
|
dependencies:
|
|
15
15
|
- !ruby/object:Gem::Dependency
|
|
16
16
|
name: guard
|