guard-zeus 2.0.1.pre.alpha.pre.87 → 2.0.1.pre.alpha.pre.89
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +8 -8
- data/README.md +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,15 +1,15 @@
|
|
1
1
|
---
|
2
2
|
!binary "U0hBMQ==":
|
3
3
|
metadata.gz: !binary |-
|
4
|
-
|
4
|
+
YjZhYTM2ZGRlYWE5NzEyOTM5YTEyMTRmMDFhYjU2NmZiY2FiMWRkNQ==
|
5
5
|
data.tar.gz: !binary |-
|
6
|
-
|
6
|
+
NGQwZDY0ZjhhODg1ODhhODE1ZDMyMjdlZjhiNWRhODk3MjcyM2QwMg==
|
7
7
|
SHA512:
|
8
8
|
metadata.gz: !binary |-
|
9
|
-
|
10
|
-
|
11
|
-
|
9
|
+
MTI0ZWFmN2Y1NjczNzg0MGZjOWU2MzA1Nzk0ZjZiYmJmNjUzMDA2NjM2YzFl
|
10
|
+
YjlkYTk0M2MwNjY3MDBiYmQ0NzdmZGNhMjdkNjY3ZWZmZjAwMmExZjM4ZDJl
|
11
|
+
ZTY0NjA3NzE1MmE5Y2I5MjE0Yzk5ODBmOTNjNWYwOWQyYzEwN2E=
|
12
12
|
data.tar.gz: !binary |-
|
13
|
-
|
14
|
-
|
15
|
-
|
13
|
+
ZGU3NjI3YzdkNTk5OWQzNWJhODg1MWNhMmRmOTA0NGU4ZDA2MzhkMjY4ZDk1
|
14
|
+
NzcwNjQ4ZTEwOWEwZWY2NDY5ZTEwNzAzZGZjZjNlODBlYjQ5NjhjNmJhNjZk
|
15
|
+
OWFkY2VkYjJiZTVhNzFkZGIwNWRjYzEzOWIyNzUwZTEyNDQ2NDg=
|
data/README.md
CHANGED
@@ -50,7 +50,7 @@ Available options:
|
|
50
50
|
Known Issues
|
51
51
|
------------
|
52
52
|
|
53
|
-
There is a known issue when using guard-
|
53
|
+
There is a known issue when using guard-zeus with pry, notably the zeus output appear on top of the pry console.
|
54
54
|
|
55
55
|
The workaround is to add the `cli` setting in your `Guardfile`, e.g.
|
56
56
|
|
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.89
|
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: 2015-06
|
13
|
+
date: 2015-07-06 00:00:00.000000000 Z
|
14
14
|
dependencies:
|
15
15
|
- !ruby/object:Gem::Dependency
|
16
16
|
name: guard
|