binding.repl 0.5.0 → 0.5.0.1

data/ChangeLog.txt

@@ -1,3 +1,7 @@
+== v0.5.0.1
+   - documentation fix
+   error in documentation
+
 == v0.5.0
    - disable {$HOME,$CWD}/.binding.repl.rc loading
    set ENV["BINDING_REPL_RC"] = 0 to disable load.

data/README.md

@@ -82,17 +82,17 @@ console they like to use and __binding.repl__ tries to accomondate by
 reading a `.binding.repl.rc` file from $HOME or the current working
 directory. It's a JSON file with a single key-value pair.
 
-amy prefers IRB, so her `$HOME/.binding.repl.rc` would look like this:
+let's say amy prefers IRB, so her `$HOME/.binding.repl.rc` would look like this:
 ```javascript
 {
   "auto_load_order": ["irb", "pry", "ripl"]
 }
 ```
 
-rob prefers pry, so his `$HOME/.binding.repl.rc` would look like this:
+let's say rob prefers pry, so his `$HOME/.binding.repl.rc` would look like this:
 ```ruby
 {
-  "auto_load_order": ["irb", "pry", "ripl"]
+  "auto_load_order": ["pry", "ripl", "irb"]
 }
 ```
 
@@ -100,7 +100,6 @@ when either rob or amy wants to start their favorite ruby console
 they can use `binding.repl.auto`:
 
 ```ruby
-# lib/foo.rb
 class Foo
   # starts "irb" in the context of Foo for amy.
   # starts "pry" in the context of Foo for rob.

data/lib/binding.repl.rb

@@ -18,7 +18,7 @@ class BindingRepl
   end
 
   def self.version
-    "0.5.0"
+    "0.5.0.1"
   end
 
   def self.add(console, predicate, runner)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: binding.repl
 version: !ruby/object:Gem::Version
-  version: 0.5.0
+  version: 0.5.0.1
   prerelease: 
 platform: ruby
 authors:
@@ -85,7 +85,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: 184924604236581946
+      hash: 3376741640928486311
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.23