pryx 0.4.3 → 0.4.4

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 +4 -4
  2. data/README.md +12 -2
  3. data/lib/pryx/version.rb +1 -1
  4. metadata +4 -4
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 6d121965f11784fd2deb6c2fbee66d4f96faa2743906a9a9b400b85065359c1b
4
- data.tar.gz: 1f90e8cd2c47468f93ad15e1254f3688b91c1e307e98261e305709693f40a4e0
3
+ metadata.gz: 4f026b0034b9947eee339d8063f5fb839e747637e2a42ba3f64b337a2851eb86
4
+ data.tar.gz: a9f544c647ef0c0a9f844d72c20fd3a2b3b754c44c0186edce2a5de080a55629
5
5
  SHA512:
6
- metadata.gz: 657a819364d7e7c648d603d5b0d924caac8ac4666f874bd3cbc4eb7920831dd889323cfcf235562918e70c3540a55f0cfe53cfc6461b51e4f4dbdc6cb8ad2856
7
- data.tar.gz: abdfabd15423b7bb21b16177ab7f20f9e276094983ae92977ee22e0f38c54dd2df78ef32289394ef06e8804b4cd847e1708ced38fef94119e4979c2655d0e34e
6
+ metadata.gz: cab620e8b026be0f92d73615cc3770dac0eb3932d20817da429a743a41e9395a3068ea0189884c7d38b0978d9204eeef0862085a50323b2991941292231aea66
7
+ data.tar.gz: '09f1655674251316bcdc7ae12cf6ce4b0cebc636b6c1f296c9f12028893b52c884a6260a2f06b43fff6efabb85785970e0d58f58a652da2915bb1e4c54504e90'
data/README.md CHANGED
@@ -81,11 +81,21 @@ but above plugins and libraries all correct configured.
81
81
 
82
82
  we have another Kernel#pry?, which enable `pry-state` automatically, see [pry-state](https://github.com/SudhagarS/pry-state)
83
83
 
84
- ### we have two binary, pryx, irbx
84
+ ### we have 3 binary, pryx, irbx, pry! installed
85
85
 
86
86
  pryx is same as pry, but, with plugins and libraries correct configured.
87
87
 
88
- irbx is same for irb.
88
+ irbx is same things for irb.
89
+
90
+ pry! is same as pry-remote command, when `pry!` was intercepted in a background process,
91
+ you can run pry! in terminal connnect to it.
92
+
93
+ if your's pry-remote server started background on another host, or on a container, you man need
94
+ specify hostname and port, e.g. connnect to 192.168.1.100, with port 9876
95
+
96
+ ```sh
97
+ $: pry! -s 192.168.1.100 -p 9876
98
+ ```
89
99
 
90
100
  ## Philosophy
91
101
 
data/lib/pryx/version.rb CHANGED
@@ -1,7 +1,7 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module Pryx
4
- VERSION = [0, 4, 3]
4
+ VERSION = [0, 4, 4]
5
5
 
6
6
  class << VERSION
7
7
  include Comparable
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: pryx
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.4.3
4
+ version: 0.4.4
5
5
  platform: ruby
6
6
  authors:
7
7
  - Billy.Zheng(zw963)
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2022-04-22 00:00:00.000000000 Z
11
+ date: 2022-04-23 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: awesome_print
@@ -156,14 +156,14 @@ dependencies:
156
156
  requirements:
157
157
  - - "~>"
158
158
  - !ruby/object:Gem::Version
159
- version: '0.4'
159
+ version: '0.5'
160
160
  type: :development
161
161
  prerelease: false
162
162
  version_requirements: !ruby/object:Gem::Requirement
163
163
  requirements:
164
164
  - - "~>"
165
165
  - !ruby/object:Gem::Version
166
- version: '0.4'
166
+ version: '0.5'
167
167
  description: ''
168
168
  email:
169
169
  - vil963@gmail.com