pryx 0.4.1 → 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.
- checksums.yaml +4 -4
- data/README.md +22 -10
- data/lib/pryx/version.rb +1 -1
- metadata +4 -4
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 4f026b0034b9947eee339d8063f5fb839e747637e2a42ba3f64b337a2851eb86
|
4
|
+
data.tar.gz: a9f544c647ef0c0a9f844d72c20fd3a2b3b754c44c0186edce2a5de080a55629
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: cab620e8b026be0f92d73615cc3770dac0eb3932d20817da429a743a41e9395a3068ea0189884c7d38b0978d9204eeef0862085a50323b2991941292231aea66
|
7
|
+
data.tar.gz: '09f1655674251316bcdc7ae12cf6ce4b0cebc636b6c1f296c9f12028893b52c884a6260a2f06b43fff6efabb85785970e0d58f58a652da2915bb1e4c54504e90'
|
data/README.md
CHANGED
@@ -2,11 +2,6 @@
|
|
2
2
|
|
3
3
|
Three Virtues of a Programmer: Laziness, Impatience, and Hubris. -- Larry Wall, the author of Perl Programming language.
|
4
4
|
|
5
|
-
|
6
|
-
## Philosophy
|
7
|
-
|
8
|
-
TODO: Write philosophy
|
9
|
-
|
10
5
|
## Getting Started
|
11
6
|
|
12
7
|
Don't add this gem into bundler's Gemfile.
|
@@ -82,17 +77,34 @@ we have irb1 and irb2 too.
|
|
82
77
|
### pry3
|
83
78
|
|
84
79
|
It just normal `binding.pry`, that is, will always be intercept if code can reach.
|
85
|
-
but above plugins and
|
80
|
+
but above plugins and libraries all correct configured.
|
86
81
|
|
87
82
|
we have another Kernel#pry?, which enable `pry-state` automatically, see [pry-state](https://github.com/SudhagarS/pry-state)
|
88
83
|
|
89
|
-
|
84
|
+
### we have 3 binary, pryx, irbx, pry! installed
|
90
85
|
|
91
|
-
|
86
|
+
pryx is same as pry, but, with plugins and libraries correct configured.
|
87
|
+
|
88
|
+
irbx is same things for irb.
|
92
89
|
|
93
|
-
|
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.
|
94
92
|
|
95
|
-
|
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
|
+
```
|
99
|
+
|
100
|
+
## Philosophy
|
101
|
+
|
102
|
+
This gem is design to maximum limit take effect current ruby program, so, it should be safe to use it.
|
103
|
+
But, you should only use it when development, though, it was tested when use in docker-compose container too.
|
104
|
+
|
105
|
+
## Support
|
106
|
+
|
107
|
+
* MRI 2.2+
|
96
108
|
|
97
109
|
## History
|
98
110
|
|
data/lib/pryx/version.rb
CHANGED
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.
|
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-
|
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.
|
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.
|
166
|
+
version: '0.5'
|
167
167
|
description: ''
|
168
168
|
email:
|
169
169
|
- vil963@gmail.com
|