pryx 0.6.1 → 0.7.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: '09a8d65224c56092b01d8230556c4ef522637b1b6e1932c5333ce018c3f0ce93'
4
- data.tar.gz: 5426012f47fa266763061e41ce8e8d45a34ab61ad0cf70de517a98312a40722b
3
+ metadata.gz: ce341aed30736e74c9555f58904c279e3df2c8e9b34927b5a3ea0a203d56f48a
4
+ data.tar.gz: b910b99fd34921918bac6baccf2153518f0ca9c46d00245e4af507f80121df1e
5
5
  SHA512:
6
- metadata.gz: 3df7840a906cbe572d6c60bda02e17b5ad5dff15568e34307a031ac7f1fdc9416445e55f62197983d7e983d769be4dc484ee722468545457e4f60c3cb6907878
7
- data.tar.gz: 864ab3c3f5ec04563fda87ccfc7f3ad25097a75495bc977a613e123de0a2228ad4afea4e1c0b1d650e0230b860cf55f654345948ab9081cffad3f791a01064fb
6
+ metadata.gz: 39b07122fe28eb18ef6b69ce6719fa59a75eb0d5aad2d6407de9684298dd9b80396a3d547294d043e8566043168ee4f14d61c22674d94efb1443f4ec9325e9a8
7
+ data.tar.gz: 335180f0b216cc9997118bf6e692b5bfb95f8a70d5cc5b1c28049f3955d96dd2696072e516a06fd963e8bb35b4fae4a006879adcf2903b929f193733ee94e791
data/README.md CHANGED
@@ -55,6 +55,18 @@ use http connection.
55
55
  Until now, you've only seen the tip of the iceberg, please have a try.
56
56
 
57
57
 
58
+ If you prefer to use IRB over Pry, use can add following code instead.
59
+
60
+ ```sh
61
+ $: export RUBYOPT+=' -rpryx_irb'
62
+ $: ruby your_file.rb # add pry! in your_file for start pry session
63
+ ```
64
+
65
+ __WARN__: `require 'pryx_irb'` will enable many gems by default in your's ruby code.
66
+ so, prefer to use `require 'pryx'`, because latter almost not affect your's code,
67
+ only several methods added into Kernel#, and gems only be require if you run invoke
68
+ those added methods.
69
+
58
70
  ## useful command which added directly to Kernel#
59
71
 
60
72
  ### Kernel#pry!
@@ -70,7 +82,7 @@ $: RUBYOPT+='-rpryx_irb' ruby your_file.rb # add irb! in your_file for start pry
70
82
 
71
83
  Following feature both available when start a Pry or IRB session:
72
84
 
73
- 1. Add `next/step/up/down` command for debug, use [break](https://github.com/gsamokovarov/break)
85
+ 1. Add `next/step/up/down` command for debug, use [break](https://github.com/gsamokovarov/break) [pry-stack_explorer](https://github.com/pry/pry-stack_explorer)
74
86
  2. Add `Kernel#ls1`(use ls1 to avoid conflict with pry builtin ls command), see [looksee](https://github.com/oggy/looksee)
75
87
  3. Use `ap` for pretty print. see [awesome-print](https://github.com/awesome-print/awesome_print)
76
88
  4. Use `Clipboard.copy` or `Clipboard.paste` to interactive with system clipboard. see [clipboard](https://github.com/janlelis/clipboard)
@@ -138,7 +150,6 @@ namespace/variables etc.
138
150
 
139
151
  But, you should only use it in development, though, it was tested is run in container(alpine) too.
140
152
 
141
-
142
153
  ## Limit
143
154
 
144
155
  1. `break` not work well if you add more than one break point, but still use `next` goto the next break point,
@@ -1,3 +1,4 @@
1
+ # power_assert is ruby 3 builtin gem
1
2
  require 'pry-power_assert'
2
3
 
3
4
  require 'pry-doc'
@@ -12,9 +13,9 @@ require 'pry-disasm'
12
13
  require 'pry-aa_ancestors'
13
14
  Pry::Commands.alias_command 'aa', 'aa_ancestors'
14
15
 
15
- # 这个必须在最后才有效, 但是目前存在一个问题,就是会将 pry3, pry! 加入 stacks
16
- # stack 显示 stack 的列表,frame 显示当前所在 stack, stack N 也可以根据数字跳转到 N
17
- require 'pry-stack_explorer' # Support: up, down, bottom, top, stack, frame
16
+ # stack 显示 stack 的列表,
17
+ # frame 显示当前所在 stack, frame N 也可以根据数字跳转到 N
18
+ require 'pry-stack_explorer'
18
19
  require 'pryx/pry-stack_explorer_hack'
19
20
 
20
21
  Pry::Commands.block_command 'cc', 'Continue, but stop in pry! breakpoint' do
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, 6, 1]
4
+ VERSION = [0, 7, 0]
5
5
 
6
6
  class << VERSION
7
7
  include Comparable
data/lib/pryx.rb CHANGED
@@ -9,7 +9,7 @@ require 'pryx/irb_hack'
9
9
 
10
10
  # Add the non-bundler managermented gems back
11
11
  # this step is necessory when install pryx in docker-compose
12
- ENV['RUBYLIB'] = $LOAD_PATH.grep(/gems/).join(':')
12
+ ENV['RUBYLIB'] = "#{ENV['RUBYLIB']}:#{$LOAD_PATH.grep(/gems/).join(':')}"
13
13
 
14
14
  # set export RUBYOPT+=" -rpryx" to work with pryx.
15
15
  module Pryx
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.6.1
4
+ version: 0.7.0
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-24 00:00:00.000000000 Z
11
+ date: 2022-04-25 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: awesome_print