pryx 0.8.7 → 0.9.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 21ef7733a26e73d29f2b967c8f1aa997a93a8aa0ada5b523380bbb611d124857
-  data.tar.gz: fb57517c9c3f1fb4e0b28134e084ca9ac0d9372ccf142f8755d7b1684f50de03
+  metadata.gz: 7d22d1022ace2897c46d58d4c3f91ff8f8e9ff62779c2616ddd36744c341215a
+  data.tar.gz: 7d89e918eddfabf381c58de5562ff6bb31aead8cd94d9e111b795c6654fa9729
 SHA512:
-  metadata.gz: c347c7fa051a6c19f3c00ea12dd8e2965ad4d9881aa24c394da7d0c213251bd2c118fec08e1f24e0d48d606861fcdb165e1ff71eac56132857271466592627cc
-  data.tar.gz: 873ac59fee702003cb843a298f45c5db17af92be0a90fa1d5e768ab96a93dc62d0d9116e4ab6ed9336ed0babfedda9e83dbc9beab6693f1514a018250ab87307
+  metadata.gz: 8d3e16ce72313a3fdec2b50a0740b4c2eb65338b33a66cb46bfee4594969e9be5fce99e5c1fa85a317e7e1397f787217bc475fd05ef4f14032b2ef5ddee865cf
+  data.tar.gz: 5bc99437dc472551b5faddc4012b283fa56e1da7c61ae4713ea5cad5d90561194ec81cc6c3487245e93548dc3cf25598e20e89fdd666a373a48b88d494bcae4b

data/README.md

@@ -1,4 +1,4 @@
-# Pryx [![Build Status](https://travis-ci.com/zw963/pryx.svg?branch=master)](https://app.travis-ci.com/github/zw963/pryx)[![Gem Version](https://badge.fury.io/rb/pryx.svg)](http://badge.fury.io/rb/pryx)![](https://ruby-gem-downloads-badge.herokuapp.com/pryx?type=total)
+# Pryx [![CI](https://github.com/zw963/pryx/actions/workflows/ci.yml/badge.svg)](https://github.com/zw963/pryx/actions/workflows/ci.yml)[![Gem Version](https://badge.fury.io/rb/pryx.svg)](http://badge.fury.io/rb/pryx)![](https://ruby-gem-downloads-badge.herokuapp.com/pryx?type=total)
 
 Three Virtues of a Programmer: Laziness, Impatience, and Hubris. -- Larry Wall, the author of Perl Programming language.
 
@@ -10,7 +10,7 @@ Instead, install it directly via RubyGems
 
     $ gem install pryx
 	
-Then use can use pryx cross all your's project.	
+Then user can use pryx cross all your's project.	
 
 ## Usage
 
@@ -26,13 +26,14 @@ $: ruby your_file.rb              # add pry! in your_file for start pry session
 
 or Run your's code directly use:
 
+
 ```sh
 $: RUBYOPT+='-rpryx' ruby your_file.rb  # add pry! in your_file for start pry session
 ```
 
 Then, try add `pry!` into your's ruby code, then run it, have fun!
 
-Following is a example, assume we have test.rb, it content like this:
+Following is a example, assume there is a `test.rb` with content:
 
 ```rb
 # test.rb
@@ -51,58 +52,46 @@ use http connection.
 
 ![pry_remote.png](images/pry_remote.png)
 
-
 Until now, you've only seen the tip of the iceberg, please have a try.
 
 
-If you prefer to use IRB over Pry, use can add following code instead.
-
-```sh
-$: export RUBYOPT+=' -rpryx_irb'
-$: ruby your_file.rb              # add pry! in your_file for start pry session
-```
+the preferred way to use pryx is add `export RUBYOPT+=' -rpryx'` to system start script.
 
-__WARN__: `require 'pryx_irb'` will enable many gems by default in your's ruby code.
-so, prefer to use `require 'pryx'`, because latter almost not affect your's code,
-only several methods added into Kernel#, and gems only be require if you run invoke
-those added methods.
+It should almost not affect your's code too much, only special methods defined into Kernel#, 
+no any gem be required before you invoke those added methods.
 
 ## useful command which added directly to Kernel#
 
-### Kernel#pry!   
-   
+### Kernel#pry!
+
 start a pry session, this session only can be intercept once if add into a loop.
 when used with a rails/roda web server, it only intercept one per request.
 
-we have IRB equivalent, named `irb!`, for use more nice feature, use following code instead:
-
-```sh
-$: RUBYOPT+='-rpryx_irb' ruby your_file.rb # add irb! in your_file for start pry session
-```
+we have IRB equivalent, named `irb!`, though, only a little feature support it.
 
 Following feature both available when start a Pry or IRB session:
 
-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)
-2.  Add `Kernel#ls1`(use ls1 to avoid conflict with pry builtin ls command), see [looksee](https://github.com/oggy/looksee)
-3.  Use `ap` for pretty print. see [awesome-print](https://github.com/awesome-print/awesome_print)
-4.  Use `Clipboard.copy` or `Clipboard.paste` to interactive with system clipboard. see [clipboard](https://github.com/janlelis/clipboard)
+1.  Add `Kernel#ls1`(use ls1 to avoid conflict with pry builtin ls command), see [looksee](https://github.com/oggy/looksee)
+2.  Use `ap` for pretty print. see [awesome-print](https://github.com/awesome-print/awesome_print)
+3.  Use `Clipboard.copy` or `Clipboard.paste` to interactive with system clipboard. see [clipboard](https://github.com/janlelis/clipboard)
 
-Following is pry command available only after start a Pry session:
+Following feature available only for a Pry session:
 
-1.  Add `$/?` command for see source, see [pry-doc](https://github.com/pry/pry-doc)
-2.  pry-remote debug support. you still use `pry!` no changes, it will use `pry-remote` automatically
+1.  Add `next/step/continue/up/down` command for debug, use [pry-nav](https://github.com/nixme/pry-nav) [pry-stack_explorer](https://github.com/pry/pry-stack_explorer)
+2.  Add `$/?` command for see source, see [pry-doc](https://github.com/pry/pry-doc)
+3.  pry-remote debug support. you still use `pry!` no changes, it will use `pry-remote` automatically
     if current ruby process was running on backround, then, it will use pry-remote, and listen on 0.0.0.0:9876,
     Then, you can connect to it from another terminal! see [pry-remote](https://github.com/Mon-Ouie/pry-remote)
-3.  Add `pa` command, see [pry-power_assert](https://github.com/yui-knk/pry-power_assert)
-4.  Add `hier` command for print the class hierarchies, see [pry-hier](https://github.com/phaul/pry-hier)
-5.  Add `pry-aa_ancestors` command for print the class hierarchy, see [pry-aa_ancestors](https://github.com/tbpgr/pry-aa_ancestors)
-6.  Add `up/down/frame/stack` command, see [pry-stack_explorer](https://github.com/pry/pry-stack_explorer)
-7.  Add `yes` or `y` command, see [pry-yes](https://github.com/christofferh/pry-yes)
+4.  Add `pa` command, see [pry-power_assert](https://github.com/yui-knk/pry-power_assert)
+5.  Add `hier` command for print the class hierarchies, see [pry-hier](https://github.com/phaul/pry-hier)
+6.  Add `pry-aa_ancestors` command for print the class hierarchy, see [pry-aa_ancestors](https://github.com/tbpgr/pry-aa_ancestors)
+7.  Add `up/down/frame/stack` command, see [pry-stack_explorer](https://github.com/pry/pry-stack_explorer)
+8.  Add `yes` or `y` command, see [pry-yes](https://github.com/christofferh/pry-yes)
 9.  Add `pry-disam`, Check following screenshot for a example:
 
 ![pry-disasm](images/disasm.png)
 
-### Kernel#pry1 Kernel#pry2  (sorry for this bad name, please create a issue you have a better one)
+### Kernel#pry1 Kernel#pry2  (sorry for the bad name, please create a issue you have a better one)
 
 pry2 do nothing, but it will be interceptd and start a pry session only after pry1 is running.
 
@@ -153,8 +142,10 @@ But, you should only use it in development, though, it was tested is run in cont
 
 ## Limit
 
-  1. `break` not work well if you add more than one break point, but still use `next` goto the next break point,
-     See https://github.com/gsamokovarov/break/issues/12
+  1. When use looksee with irb for Ruby 3.1.x, looksee output color was not correct displayed.
+     check: https://github.com/oggy/looksee/issues/57
+  2. Pry's show auto-watch when not work, because `Enter` key rebinding to `run the last command`.
+     i consider this is more useful, you can always use `w` alias to see the watch changes.
 
 ## Support
 

data/bin/irbx

@@ -9,4 +9,8 @@
 require 'irb'
 require 'pryx_cli'
 
+# Fix `irb: warn: can't alias ls from irb_ls` issue.
+# See: https://github.com/oggy/looksee/issues/56
+Looksee.rename :_ls
+
 IRB.start(__FILE__)

data/bin/pryx

@@ -7,8 +7,8 @@
 $0 = 'pry'
 
 require 'pry'
-require 'pryx/pry_plugins'
 require 'pryx_cli'
+require 'pryx/pry_plugins'
 
 # Process command line options and run Pry
 opts = Pry::CLI.parse_options

data/lib/pryx/ap_hack.rb

@@ -8,6 +8,7 @@ if defined? AwesomePrint
   if defined? Pry
     AwesomePrint.pry!
   else
+    # auto ap only works when running with `irbx`
     AwesomePrint.irb!
   end
 end

data/lib/pryx/common_plugins.rb

@@ -1,12 +1,2 @@
-require 'binding_of_caller'
 require 'clipboard'
-
-# HACK: for ap 可以确保，当使用 irb! 时，looksee ls1 输出显示正确，同时不用关闭 irb :USE_COLORIZE 设置。
-# See https://github.com/oggy/looksee/issues/57
-# 但是，ap_hack 必须放到 break_hack 前面，调换顺序，上面的 hack 失效。
-# WARN: 下面两行 require 代码顺序不要换。
 require 'pryx/ap_hack'
-require 'break'
-Pry.commands.alias_command 'n', 'next'
-Pry.commands.alias_command 's', 'step'
-Pry.commands.alias_command 'w', 'watch' # watch is pry builtin

data/lib/pryx/irb_hack.rb

@@ -2,17 +2,7 @@ class Binding
   def _irb(_host=nil)
     warn 'loading irb ...'
 
-    if defined? Break and defined? IRB
-      # This is need for work with looksee better.
-      # See discuss on https://github.com/oggy/looksee/issues/57
-      IRB.conf[:USE_COLORIZE] = false
-    else
-      warn "For work with Break and Looksee, please set
-export RUBYOPT='-rpryx_irb'
-instead of
-export RUBYOPT='-rpryx'
-"
-    end
+    require 'pryx/common_plugins'
 
     self.irb
   end
@@ -24,8 +14,6 @@ module Kernel
 
     ENV['IRB_was_started'] = 'true'
 
-    require 'binding_of_caller'
-
     irb3(2)
   end
 
@@ -40,9 +28,6 @@ module Kernel
   def irb2
     if ENV['IRB2_should_start'] == 'true'
       ENV['IRB2_should_start'] = nil
-
-      require 'binding_of_caller'
-
       irb3(2)
     end
   end

data/lib/pryx/looksee_hack.rb

@@ -11,12 +11,8 @@
 
 module Kernel
   def _load_looksee
-    case RbConfig::CONFIG['ruby_version']
-    when '1.9.0'...'2.1.0'
-      require 'old_looksee'
-    when '2.1.0'...'3.2.0'
-      require 'looksee'
-    end
+    require 'looksee'
+
     Looksee.rename :ls_looksee
 
     Looksee.editor = '.emacsclient +%l %f' # e.g. [].ls1.edit :to_set

data/lib/pryx/pry_hack.rb

@@ -9,6 +9,8 @@ class Binding
     end
 
     require 'pryx/common_plugins'
+
+    # NOTICE: Ensure pry-navs (in pry_plugins) always required after pry-remote
     require 'pryx/pry_plugins'
 
     if host

data/lib/pryx/pry_plugins.rb

@@ -17,8 +17,10 @@ Pry::Commands.alias_command 'aa', 'aa_ancestors'
 require 'pry-stack_explorer' # Add command `up/down/frame[n]/stack`
 require 'pryx/pry-stack_explorer_hack'
 
+require 'pry-nav'
+
 # Add command `cc`
-Pry::Commands.block_command 'cc', 'Continue, but stop in pry! breakpoint' do
+Pry::Commands.block_command 'cc', 'Continue, but stop in pry! breakpoint too' do
   Pry.instance_variable_set(:@initial_session, true)
   ENV['Pry_was_started'] = nil
   throw(:breakout)
@@ -26,7 +28,9 @@ end
 
 Pry.commands.alias_command 'wai', 'whereami' # Add command alias `wai`
 
-# Hit Enter repeat last command
+# Hit Enter repeat last command, this feature will make auto-watch unavailable.
 Pry::Commands.command(/^$/, 'repeat last command') do
-  pry_instance.run_command Pry.history.to_a.last
+  run Pry.history.to_a.last
 end
+# So, add a new alias w for user use it manually
+Pry.commands.alias_command 'w', 'watch' # watch is pry builtin

data/lib/pryx/version.rb

@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module Pryx
-  VERSION = [0, 8, 7]
+  VERSION = [0, 9, 2]
 
   class << VERSION
     include Comparable

data/lib/pryx_cli.rb

@@ -1,12 +1,7 @@
-require 'clipboard'
-
-require 'pryx/ap_hack'
-
 # This require is needed, because can't require looksee in method when use with bundler.
 # bundler remove looksee from $LOAD_PATH when start with rails.
 require 'looksee'
-require 'pryx/looksee_hack'
-
+require 'pryx/common_plugins'
 require 'pryx'
 
 if File.exist? 'config/environment.rb'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: pryx
 version: !ruby/object:Gem::Version
-  version: 0.8.7
+  version: 0.9.2
 platform: ruby
 authors:
 - Billy.Zheng(zw963)
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2022-07-08 00:00:00.000000000 Z
+date: 2022-10-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: awesome_print
@@ -25,61 +25,61 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '1.9'
 - !ruby/object:Gem::Dependency
-  name: break
+  name: clipboard
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.40.0
+        version: '1.3'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.40.0
+        version: '1.3'
 - !ruby/object:Gem::Dependency
-  name: clipboard
+  name: pry
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.3'
+        version: '0.14'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.3'
+        version: '0.14'
 - !ruby/object:Gem::Dependency
-  name: looksee
+  name: pry-nav
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '4.4'
+        version: 1.0.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '4.4'
+        version: 1.0.0
 - !ruby/object:Gem::Dependency
-  name: pry
+  name: looksee
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.14'
+        version: '4.4'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.14'
+        version: '4.4'
 - !ruby/object:Gem::Dependency
   name: pry-aa_ancestors
   requirement: !ruby/object:Gem::Requirement
@@ -182,16 +182,16 @@ dependencies:
   name: minitest
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - '='
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 5.15.0
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - '='
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 5.15.0
 - !ruby/object:Gem::Dependency
   name: ritual
   requirement: !ruby/object:Gem::Requirement
@@ -247,7 +247,6 @@ files:
 - lib/pryx/trap_backtrace.rb
 - lib/pryx/version.rb
 - lib/pryx_cli.rb
-- lib/pryx_irb.rb
 homepage: http://github.com/zw963/pryx
 licenses:
 - MIT
@@ -268,7 +267,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.3.3
+rubygems_version: 3.3.7
 signing_key:
 specification_version: 4
 summary: pry extension tools!

data/lib/pryx_irb.rb

@@ -1,9 +0,0 @@
-# We need apply those hack before irb was loaded for work with irb.
-# So we have to add it here, same hacks for Pry is add to method
-# Binding#_pry which defined in lib/pryx/pry_hack.rb
-
-# we need set `export RUBYOPT+=" -rpryx_irb"` instead of `-rpryx` to make
-# irb work with break and ap gem.
-
-require 'pryx/common_plugins'
-require 'pryx'