guard-zeus 2.0.1.pre.alpha.pre.87 → 2.0.1.pre.alpha.pre.89

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 (3) hide show
  1. checksums.yaml +8 -8
  2. data/README.md +1 -1
  3. metadata +2 -2
checksums.yaml CHANGED
@@ -1,15 +1,15 @@
1
1
  ---
2
2
  !binary "U0hBMQ==":
3
3
  metadata.gz: !binary |-
4
- MDk2MGVhOWE0ODZjNGNhMzk3Mzc3ZDhhMzRkYmY1ZmZlMzkwM2M0MA==
4
+ YjZhYTM2ZGRlYWE5NzEyOTM5YTEyMTRmMDFhYjU2NmZiY2FiMWRkNQ==
5
5
  data.tar.gz: !binary |-
6
- MjhkMjQwMDJkZDc0ZmFlNGQwYWViZmM3MmQ2OGVhNzM4OTBhMzg5OA==
6
+ NGQwZDY0ZjhhODg1ODhhODE1ZDMyMjdlZjhiNWRhODk3MjcyM2QwMg==
7
7
  SHA512:
8
8
  metadata.gz: !binary |-
9
- N2RjMTRhNWY0MmE3Yzc4ZGIxOWIwYmM5YTExZWZmNTgwNDEzMmNhNDJkOGYw
10
- YThlYmRlYTg3ZmY0NDM1ZGViNTYwMzJjZWU3MWI5YzBkMWM2NDlhZWVlZDU5
11
- NjIzNjJjMzUzNjJlMzkwYWE1ZGFiYjgyNGY3ZWZlMTQyOTJmYjE=
9
+ MTI0ZWFmN2Y1NjczNzg0MGZjOWU2MzA1Nzk0ZjZiYmJmNjUzMDA2NjM2YzFl
10
+ YjlkYTk0M2MwNjY3MDBiYmQ0NzdmZGNhMjdkNjY3ZWZmZjAwMmExZjM4ZDJl
11
+ ZTY0NjA3NzE1MmE5Y2I5MjE0Yzk5ODBmOTNjNWYwOWQyYzEwN2E=
12
12
  data.tar.gz: !binary |-
13
- ZTY2OTcyNTVkNzZjY2ZlMzEzY2EyNDM4Y2I2NGZhOTNhNWYxYTk3ZDI5MWYx
14
- ZjA2NjA3MjhlMDBjNmI0NmVlMTg0YjQxOGI3NmI3NGI3NjVmZTQ4MDkxOWNl
15
- ZDY4MTRjNDNjNWQ5MDVhMTJmMjVlMGQwYTdiNGExZTkyOTdjYjU=
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-zues with pry, notably the zeus output appear on top of the pry console.
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.87
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-02 00:00:00.000000000 Z
13
+ date: 2015-07-06 00:00:00.000000000 Z
14
14
  dependencies:
15
15
  - !ruby/object:Gem::Dependency
16
16
  name: guard