pry-try 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 9be4107b9a3260e37eab98cd327a3ce9cd76133c
-  data.tar.gz: ecb09c7a053714d9ecdb747ea6d9de8b52c9fa65
+  metadata.gz: 42dc31f96ce666efa506a7d4eb1818c962517547
+  data.tar.gz: aa56f8839c0a5230092967144e31ef8c930f873b
 SHA512:
-  metadata.gz: a493f0705ccdeadf414858b67727abcf293c5b627eb40d6f3edb29fd907c6bf5357b24f1ea0c85817aca04d1c22d551c3b3674cef504b0ae5c1a2e3750e5172a
-  data.tar.gz: b043e9a41d84205dca42dfe001946af3817fe591cfe07cc27a23cabb4f22abfe10ea9d00401bb5ff6cc67dba190904f06e34f1cc4bd4f3c8fa9f00fc47225f6c
+  metadata.gz: ab07fa47a0def00a6674df5e061a7434d48f49528d52be5da56258703e81fd606f7f9a6155e5dc70cd5a9214d52b90b94073771d87dbf6bb536e0d8e1b9b3eae
+  data.tar.gz: 83cfcbd300813197a593310db9c4f73bf335d0294d094237c35fcb02c6acc90c0fa4d10d4347d752d0729b7ec821faebbd0c31243352ae8a548eae7ddb8c4e0d

data/README.md

@@ -1,73 +1,81 @@
 # pry-try
 
-Open a pry-session with the gems you want to try.  
+Start a pry-session with specific gems or a (remote) script loaded.
 
 ## Usage
 
-This gem should supports the following usecases:
-
-### pipe-in a script
-
-```bash
-# piped-in content is evaluated in a new pry-session:
-$ echo '@a = 1' | pry-try
-[1] pry(main)> @a =1
-1
-[2] pry(main)> 
-
-# handy to share scripts with others:
-$ curl <path-to-raw-gist> | pry-try
-```
-
-### try a gem
-
-Start a new pry-session with the requested gems loaded:
-
-```bash
-$ pry-try activesupport
-Fetching gem metadata from https://rubygems.org/.........
-Fetching version metadata from https://rubygems.org/.
-Resolving dependencies...
-Using concurrent-ruby 1.0.5
-Using i18n 0.8.1
-Using minitest 5.10.1
-Using thread_safe 0.3.6
-Using coderay 1.1.1
-Using method_source 0.8.2
-Using slop 3.6.0
-Using bundler 1.14.5
-Using tzinfo 1.2.2
-Using pry 0.10.4
-Using activesupport 5.0.2
-[2] pry(main)> 1.second
-=> 1 second
-```
-
-Request a specific version, like you would do in a Gemfile:
-```bash
-$ pry-try activesupport '~>4.2'
-# or multiple gems:
-$ pry-try activesupport '~>4.2' redis
-```
-
-### try a gem within a pry-session
-
-```bash
-# given 
-$ pry
-[1] pry(main)> .pry-try 'activesupport'
-...
-[2] pry(main)> 1.second
-=> 1 second
-# ^D lets you return to the original pry-session
-```
+* start a pry-session with one or more gems loaded:
+
+    ```bash
+    $ pry-try activesupport
+    Fetching gem metadata from https://rubygems.org/.........
+    Fetching version metadata from https://rubygems.org/.
+    Resolving dependencies...
+    Using concurrent-ruby 1.0.5
+    Using i18n 0.8.1
+    Using minitest 5.10.1
+    Using thread_safe 0.3.6
+    Using coderay 1.1.1
+    Using method_source 0.8.2
+    Using slop 3.6.0
+    Using bundler 1.14.5
+    Using tzinfo 1.2.2
+    Using pry 0.10.4
+    Using activesupport 5.0.2
+    [2] pry(main)> 1.second
+    => 1 second
+    ```
+    
+    Use a specific version:
+    
+    ```bash
+    $ pry-try activesupport '~>4.2'
+    ...
+    [2] pry(main)>
+    ```
+        
+    Multiple gems:
+    
+    ```bash
+    $ pry-try activesupport '~>4.2' redis
+    ...
+    [2] pry(main)>
+    ```
+    
+* start pry-session from within pry:
+
+    ```bash
+    $ pry
+    [1] pry(main)> .pry-try activesupport
+    ...
+    [2] pry(main)> 
+    This session is isolated from the initial session.
+    ^d to return to initial session
+    ```
+    
+* pipe-in script and start a pry-session:
+
+    ```bash
+    $ echo '@a = 1' | pry-try
+    [1] pry(main)> @a
+    => 1
+    [2] pry(main)> 
+    
+    # handy when sharing code with others:
+    $ curl https://gist.githubusercontent.com/eval/76955c57512c1e4ac01cdd913b76c92d/raw/bf714a15789eca3e968c3544f85b9b786b8eae8f/hello.rb | pry-try
+    
+    # or via the gist command:
+    $ gist -r 76955c57512c1e4ac01cdd913b76c92d | pry-try
+    ```
+    
+    **NOTE:** curl-pipe-runtime is [not without risk](https://www.idontplaydarts.com/2016/04/detecting-curl-pipe-bash-server-side/). A tool like [vipe](https://github.com/madx/moreutils/blob/master/vipe) ([npm variant](https://github.com/juliangruber/vipe#vipe)) allows you to inspect the fetched script before handing it over to pry-try.
 
 
 ## Installation
 
 Install system-wide:
 
-    $ gem install prytry
+    $ gem install pry-try
 
 
 ## Development

data/lib/pry-try/version.rb

@@ -1,3 +1,3 @@
 module PryTry
-  VERSION = "0.2.0"
+  VERSION = "0.2.1"
 end

data/pry-try.gemspec

@@ -9,8 +9,8 @@ Gem::Specification.new do |spec|
   spec.authors       = ["Gert Goet"]
   spec.email         = ["gert@thinkcreate.nl"]
 
-  spec.summary       = %q{try a gem or script}
-  spec.description   = %q{try a gem or script}
+  spec.summary       = %q{Quickly try a gem or script on the repl}
+  spec.description   = %q{Start a pry-session with specific gems or a (remote) script loaded.}
   spec.homepage      = "https://gitlab.com/eval/pry-try/tree/master#pry-try"
   spec.license       = "MIT"
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pry-try
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Gert Goet
@@ -66,7 +66,7 @@ dependencies:
     - - "~>"
       - !ruby/object:Gem::Version
         version: '3.0'
-description: try a gem or script
+description: Start a pry-session with specific gems or a (remote) script loaded.
 email:
 - gert@thinkcreate.nl
 executables:
@@ -110,5 +110,5 @@ rubyforge_project:
 rubygems_version: 2.5.2
 signing_key: 
 specification_version: 4
-summary: try a gem or script
+summary: Quickly try a gem or script on the repl
 test_files: []