Skip to content
Browse files

WIP updating docs and screenshot...

  • Loading branch information...
1 parent 241b04b commit b92884974bfa4f6f923f160ed637462ae4057fb7 @godfat committed
Showing with 119 additions and 470 deletions.
  1. +0 −203 2011-02-28.md
  2. +0 −86 CHANGES
  3. +5 −0 CHANGES.md
  4. +0 −48 EXAMPLE.md
  5. +89 −118 README.md
  6. +0 −6 TODO
  7. +9 −0 TODO.md
  8. +16 −9 rib.gemspec
  9. BIN screenshot.png
View
203 2011-02-28.md
@@ -1,203 +0,0 @@
-[original text](http://blogger.godfat.org/2011/02/ripl-rc-1-ripl-irb-replacement.html)
-
-# ripl, an irb replacement
-
-<p></p><a href="http://www.urbandictionary.com/define.php?term=TL%3BDR">TL;DR</a>: see the <a href="#comparison">comparison table/list</a> on
-the bottom of this post. Still TL;DR?
-<pre><code>&gt; gem install ripl
-&gt; ripl rc</code></pre>
-<img src="https://github.com/godfat/ripl-rc/raw/ripl-rc-0.1.3/screenshot.png"/>
-
-Use it in rails console?
-<pre><code>&gt; gem install ripl-rails
-&gt; ripl rc rails</code></pre>
-
-# ripl
-
-Days ago when I was using <a href="https://github.com/banister/pry">pry</a> to debug heroku-scaler,
-(which is a <a href="https://github.com/Ramaze/ramaze">ramaze</a> and <a href="https://github.com/igrigorik/em-http-request">em-http-request</a> application),
-I wanted to make pry use irb history to easy debugging,
-and then I found it was talking about something like
-pry is not an irb replacement, to find an irb replacement,
-see <a href="https://github.com/cldwalker/ripl">ripl</a>. That's where I started playing around with ripl.
-
-At first, I didn't think I need an replacement for irb,
-because it worked for me. But as always, we don't know
-if we need a better tool until we're really using a better
-tool. ripl is this kind of story for me, and so do <a href="https://github.com/lsegal/yard">yard</a> to
-<a href="https://github.com/rdoc/rdoc">rdoc</a> and so on so forth. Interestingly, this is not always
-true for all tools. For example, I like <a href="https://github.com/jimweirich/rake">rake</a> better than
-<a href="https://github.com/wycats/thor">thor</a> (though I didn't really try thor), and didn't really
-need the power of <a href="http://www.kuwata-lab.com/erubis/">erubis</a> over erb.
-
-One can think that, using thor/erubis might force others
-to do the same (though erubis could be used as a drop-in
-replacement for erb), but irb/ripl is just a personal tool
-instead of really a library that once you used it in the
-application, all developers would be forced to use or test
-against it, too. Just like a text editor. Personal taste only..
-
-Back to topic...
-
-So what would we benefit from switching irb to ripl? If
-we're only using the core functionality of ripl, then not
-even talking about gains, but we'll lose some features
-that irb provides but ripl doesn't. What good is, according
-to the <a href="https://github.com/cldwalker/ripl/blob/v0.3.2/README.rdoc">README</a> of ripl, the code size was about ~270
-lines vs 5,000+ lines, so we can expect that ripl is a lot
-easier to extend and customize, and this is also a fact.
-
-ripl is designed to be extended and customized from the
-beginning, and since the code is very modular and
-lightweight, it's very easy to replicate irb's behavior
-and features that are missing in ripl. You can take a look
-at ripl-irb. It might grow to be fat after installing many
-plugins and extensions, but I guess it will never reach
-the size of irb, since irb *has its own ruby parser*...
-<a href="https://github.com/janlelis/ripl-multi_line">ripl-multi_line</a> uses a trick that catches syntax error
-exception to achieve multiline support. This might be
-tricky because it depends on the error message coming
-from syntax error; however irb's own ruby parser might
-not be accurate as well... as long as it's not using ruby's
-own parser.
-
-At first I was trying to add some simple patches with only
-a few of lines to the core of ripl to make it better, but the
-author only accepted my bug fix patches instead of features
-patches, even it's only a few of lines and I don't see why
-others won't want that features. Sometimes this make me
-feel like vim or bash, you'll definitely want some personal
-(might not be so personal though) config files instead of
-using the defaults, which is very different than GUI
-applications, which always try to provide the best defaults.
-I think both have their strength, and I don't mind as long
-as it could be customized to suit my flavor, and that's why
-I've written <a href="https://github.com/godfat/ripl-rc">ripl-rc</a>.
-
-ripl-rc is a ripl plugins collection, each of its require is a
-different plugin. For example:
-<pre><code>require 'ripl/rc/color'
-require 'ripl/rc/anchor'</code></pre>
-The first line would enable colorizing plugin, and the latter
-would enable pry session like plugin. The reason I do this
-instead of releasing ripl-color, ripl-anchor, etc., is I think
-it's a lot easier to maintain and install as a plugin collection,
-since each plugin has only a few of codes. We can take
-advantage of fixing plugins at the same time, too, since
-some plugins would work with other plugins. (e.g.
-ripl/rc/anchor and ripl/rc/color) It would be tedious for
-users and developers to release or update a bunch of new
-releases... I really hate rails doing that, though the code
-base is not the same level. It might be a must for rails
-somehow...
-
-Enough of rubbish, let's see the comparison.<a id="comparison"></a>
-
-# Comparison
-
-ripl has:
-
-* a lot fewer codes and is a lot easier to customize
-* better auto-complete (from <a href="https://github.com/cldwalker/bond">bond</a>)
-
-irb has:
-
-* multiline support (ripl uses ripl-multi_line)
-* subsessions and workspaces (actually I don't know
- what are they, never used. ripl uses <a href="https://github.com/cldwalker/ripl-commands">ripl-commands</a>)
-
-ripl-rc has, upon session ends:
-
-* <span style="color:gold">require 'ripl/rc/squeeze_history'</span>
-
- which squeezes the same input in history, both in memory
- and history file.
-
-* <span style="color:gold">require 'ripl/rc/mkdir_history'</span>
-
- which calls `mkdir -p` on directory which contains history
- file. For example, I put my irb_history in an directory
- might not exist before use: `~/.config/irb/irb_history`
-
-* <span style="color:gold">require 'ripl/rc/ctrld_newline'</span>
-
- ruby 1.9.2 has no this problem in irb, but 1.8 and ripl do.
- When hitting ctrl+d to exit ripl, it would print a newline
- instead of messing up with shell prompt.
-
-upon formatting output:
-
-* <span style="color:gold">require 'ripl/rc/strip_backtrace'</span>
-
- ripl prints the full backtrace upon exceptions, even the
- exceptions come from interactive environment, making it
- very verbose. This ripl plugin strips those backtrace.
-
-* <span style="color:gold">require 'ripl/rc/color'</span>
-
- There's ripl-color_result that make use of <a href="https://github.com/michaeldv/awesome_print">awesome_print</a>,
- <a href="http://coderay.rubychan.de/">coderay</a>, or <a href="https://github.com/janlelis/wirb">wirb</a>. The problem of awesome_print is it's too
- awesome and too verbose, and the problem of coderay and
- wirb is that they are both parser based. In ripl, this should
- be as simple as just print different colors upon different
- objects, instead of inspecting it and parsing it.
-
- ripl/rc/color just uses a hash with Class to color mapping
- to pick up which color should be used upon a ruby object.
-
- To customize the color schema, inspect `Ripl.config[:rc_color]`
-
-upon input:
-
-* <span style="color:gold">require 'ripl/rc/multiline'</span>
-
- I need some modification on ripl-multi_line to make prompt
- work better, but not sure if I can come up a good fix and
- try to convince the author to accept those patches. So I
- just bundle and maintain it on my own. If you're using
- ripl-rc, you could use this plugin, otherwise, keep using
- ripl-multi_line.
-
-* <span style="color:gold">require 'ripl/rc/eat_whites'</span>
-
- irb will just give you another prompt upon an empty input,
- while ripl would show you that your input is nil. I don't like
- this, because sometimes I'll keep hitting enter to separate
- between inspects. This plugin would skip inspect if the input
- is empty just like irb.
-
-special tool:
-
-* <span style="color:gold">require 'ripl/rc/anchor'</span>
-
- So this is my attempt to emulate pry in ripl. Instead
- trying to make pry support irb_history, colorizing, etc.,
- I think implement pry like feature in ripl is a lot easier.
- No need to be fancy, I just need the basic functionality.
-
- To use it, use:
- <pre><code>Ripl.anchor your_object_want_to_be_viewed_as_self</code></pre>
- or
- <pre><code>Ripl.anchor binding</code></pre>
- in your code. Other than pry ripl support, you might be
- interested in <a href="https://github.com/cldwalker/ripl-rails">ripl-rails</a> and <a href="https://github.com/cldwalker/ripl-hijack">ripl-hijack</a>, too.
-
-about config:
-
-* <span style="color:gold">require 'ripl/rc/noirbrc'</span>
-
- By default ripl is reading `~/.irbrc`. I don't think this
- is what people still using irb would want, because the
- configuration is totally different. This suppress that,
- make it only read `~/.riplrc`
-
-for lazies:
-
-* <span style="color:gold">require 'ripl/rc'</span>
-
- This requires anything above for you, and is what `ripl rc`
- and `ripl rc rails` shell commands did.
-
-So that's all at the moment for <a href="https://github.com/godfat/ripl-rc/tree/ripl-rc-0.1.3">ripl-rc 0.1.3</a>. Enjoy,
-
-2010-02-28 (16:36~21:49)
View
86 CHANGES
@@ -1,86 +0,0 @@
-= ripl-rc changes history
-
-== ripl-rc 0.2.4 -- 2011-08-03
-
-* [ensure_after_loop] A plugin which would make sure after_loop is called.
- (Some plugins need to do cleaning up in after_loop)
-
-* [ anchor] Fixed a bug for buggy EditLine, which would raise
- weird exception upon calling `HISTORY == nil`.
- Now we use `.nil?` to lookup if it's nil or not.
-
-* [multiline_history] Fixed a bug when multiline evaluation raised an
- exception, it wouldn't handle the history correctly.
- Moving the handling to an ensure block fixed this.
-
-* [ squeeze_history] (Internal) Take the advantage of the new history API
-
-== ripl-rc 0.2.3 -- 2011-06-16
-
-Please read this for detail:
-http://blogger.godfat.org/2011/06/new-feature-mainly-for-anchor-in-ripl.html
-
-* [ripl-rc] Ripl.enable/disable_??? now accepts a block to ease switching.
-* [ debug] This plugin is simply calling Ripl.disable_anchor at the
- beginning, make it easier to use [anchor] to inspect a certain
- place under a certain condition. See the blog post for detail.
-
-== ripl-rc 0.2.2 -- 2011-06-01
-
-* [multiline_history ] fixed multiline_history
-* [multiline_history_file] now we have persistent multiline_history
-
-== ripl-rc 0.2.1 -- 2011-04-11
-
-* [multiline] fixed history with editline (e.g. mac's build-in ruby)
-
-== ripl-rc 0.2.0 -- 2011-04-10
-
-* [ ripl-rc] tested with MRI 1.8.7, 1.9.2 and Rubinius 1.2.3, JRuby 1.6.0
-* [ ripl-rc] fixed some conflicts with bundler
-* [ ripl-rc] internal structure rearrangement
-* [ ripl-rc] all plugins now have runtime enable/disable ability
- e.g. run `Ripl.disable_color` to disable coloring,
- `Ripl.enable_color` to enable again.
-* [multiline] some tweak to make it more accurate
-* [last_exception] save last exception in Ripl.last_exception
-
-== ripl-rc 0.1.5 -- 2011-03-26
-
-* [ bin] shows a better error message when ripl-rails can't be found
-* [ ripl-rc] made require 'ripl-rc' works like require 'ripl/rc'
-* [multiline] fixed regexp warning on ruby 1.8.7
-* [multiline] fixed history when using multiline
-
-== ripl-rc 0.1.4 -- 2011-03-01
-
-* [ color] fix syntax error; sorry, i definitely need tests.. :s
-
-== ripl-rc 0.1.3 -- 2011-02-28
-
-* [ bin] added `ripl rc` and `ripl rc rails` commands
-* [noirbrc] added that don't read ~/.irbrc by default
-* [ anchor] use short_inspect
-* [ anchor] fixed a bug that cannot display nil
-* [ color] fixed a bug that displaying some values as Object. see [9a64495]
-* [ color] colorize error output as well
-* [squeeze_history] max 500 items
-* [strip_backtrace] fixed cwd, don't trace if it's a syntax error
-
-== ripl-rc 0.1.2 -- 2011-02-25
-
-* [ rc] rearranged require order
-* [ plugin] added anchor, like pry. usage: Ripl.anchor(binding) # or obj
-* [ plugin] added multiline, which works better with anchor
-* [ plugin] added mkdir_history, which tries to mkdir -p on history directory
-* [strip_backtrace] fix functionality for custom name (anchor)
-
-== ripl-rc 0.1.1 -- 2011-02-24
-
-* [ plugin] added strip_backtrace
-* [general] now use Ripl::Rc::U.include(YourExtension) to customize details
-* [ color] use Ripl.config[:rc_color] to configure color schema
-
-== ripl-rc 0.1.0 -- 2011-02-23
-
-* release early, release often
View
5 CHANGES.md
@@ -0,0 +1,5 @@
+# Rib CHANGES
+
+## Rib 0.9.0 --
+
+* First serious release!
View
48 EXAMPLE.md
@@ -1,48 +0,0 @@
-# Rib example use case
-
-## As an interactive shell
-
-* As IRB (reads `~/.config/rib/config.rb` writes `~/.config/rib/history.rb`)
-
- rib
-
-* As Rails console
-
- rib rails
-
-* As Ramaze console
-
- rib ramaze
-
-* As a console for whichever the app in the current path
- it should be (for now, it's either Rails or Ramaze)
-
- rib auto
-
-* As a fully featured interactive Ruby shell (as ripl-rc)
-
- rib all
-
-* As a fully featured app console (yes, the commands could be used together)
-
- rib all auto # or `rib auto all`, the order doesn't really matter
-
-## As a debugging/interacting tool
-
-* Single require
-* Load config
-
-* Break point
-* Edit in place
-
-## As a shell framework
-
-* Single require
-* No automatically loading config
-
-* Essence
-* Core
-* More
-* Zore
-* All
-* App
View
207 README.md
@@ -1,175 +1,146 @@
-# ripl-rc
+# Rib
by Lin Jen-Shin ([godfat](http://godfat.org))
## LINKS:
-* [github](https://github.com/godfat/ripl-rc)
-* [rubygems](http://rubygems.org/gems/ripl-rc)
+* [github](https://github.com/godfat/rib)
+* [rubygems](http://rubygems.org/gems/rib)
## DESCRIPTION:
-ripl plugins collection, take you want, leave you don't.
+Ruby-Interactive-ruBy -- Yet another interactive Ruby shell
-## REQUIREMENTS:
-
-* Tested with MRI 1.8.7, 1.9.2 and Rubinius 1.2.3, JRuby 1.6.0
-* ripl
-
-## INSTALLATION:
-
- gem install ripl-rc
-
-## SYNOPSIS:
-
-If you don't know what is __ripl__, or just want to have an
-overview of what does __ripl-rc__ do, then you can use it as
-a command line tool:
-
- ripl rc
-
-This can be used to run rails console, too. First install
-_ripl-rails_ by `gem install ripl-rails` then run this:
-
- ripl rc rails
-
-Then you'll have a _ripl-rc_ flavored rails console without
-setting anything (i.e. `~/.riplrc`)
-
-If you already know what is _ripl_, you might want to setup
-yourself, to be better control what you might want and what
-you might not want. Then checkout FEATURES for all plugins
-you can put in `~/.riplrc`.
+Rib is based on the design of [ripl][] and the work of [ripl-rc][], some of
+the features are also inspired by [pry][]. The aim of Rib is to be fully
+featured and yet very easy to opt-out or opt-in other features. It shall
+be simple, lightweight and modular so that everyone could customize Rib.
-If you want to enable all plugins, the use this:
+[ripl]: https://github.com/cldwalker/ripl
+[ripl-rc]: https://github.com/godfat/ripl-rc
+[pry]: https://github.com/pry/pry
- require 'ripl/rc'
+## REQUIREMENTS:
-Another thing which might worth to be mentioned is
-`ripl/rc/anchor`, which is a _pry_ like feature built into
-ripl. You can embed two things into ripl, one is any object:
+* Tested with MRI 1.8.7, 1.9.2 and Rubinius 1.2, JRuby 1.6
+* All gem dependencies are optional, but it's highly recommended to use
+ Rib with [bond][] for tab completion.
- Ripl.anchor your_object_want_to_be_viewed_as_self
+[bond]: https://github.com/cldwalker/bond
-Another one is local binding inside a method:
+## INSTALLATION:
- Ripl.anchor binding
+ gem install rib
-Then you can look through local variables inside a method
-with an interactive environment. Anchor could be nested, too.
-You can anchor another object inside a _ripl_ session. The number
-shown in prompt is the level of anchors, started from 1.
+## SYNOPSIS:
![Screenshot](https://github.com/godfat/ripl-rc/raw/master/screenshot.png)
-Please read this blog post for other detail since I haven't
-had time to update this README... Sorry about that.
+### As an interactive shell
+
+As IRB (reads `~/.config/rib/config.rb` writes `~/.config/rib/history.rb`)
-* [a new feature mainly for anchor in ripl-rc ](http://blogger.godfat.org/2011/06/new-feature-mainly-for-anchor-in-ripl.html)
+ rib
-## FEATURES:
+As Rails console
-upon session ends:
+ rib rails
-* `require 'ripl/rc/squeeze_history'`
+As Ramaze console
- Which squeezes the same input in history, both in memory
- and history file.
+ rib ramaze
-* `require 'ripl/rc/mkdir_history'`
+As a console for whichever the app in the current path
+it should be (for now, it's either Rails or Ramaze)
- Which calls `mkdir -p` on directory which contains history
- file. For example, I put my irb_history in an directory
- might not exist before use: `~/.config/irb/irb_history`
+ rib auto
-* `require 'ripl/rc/ctrld_newline'`
+As a fully featured interactive Ruby shell (as ripl-rc)
- Ruby 1.9.2 has no this problem in irb, but 1.8 and ripl do.
- When hitting ctrl+d to exit ripl, it would print a newline
- instead of messing up with shell prompt.
+ rib all
-upon exception occurs:
+As a fully featured app console (yes, some commands could be used together)
-* `require 'ripl/rc/last_exception'`
+ rib all auto # or `rib auto all`, the order doesn't really matter
- We can't access $! for last exception because input evaluation
- is not in the block which rescues the exception, neither can we
- update $! because it's a read only pseudo global variable.
+You can customize Rib's behaviour by setting `~/.config/rib/config.rb` (by
+default). Since it's merely a Ruby script which would be loaded into memory
+before launching Rib shell session, You can put any customization or monkey
+patch there. Personally, I use all plugins provided by Rib.
- This plugin makes last rescued exception stored in `Ripl.last_exception`
+<https://github.com/godfat/dev-tool/blob/master/.config/rib/config.rb>
-upon formatting output:
+As you can see, putting `require 'rib/all'` into config file is exactly the
+same as running `rib all` without a config file. What `rib all` would do is
+merely require the file, and that file is also merely requiring all plugins.
+Suppose you only want to use the core plugins and color plugin, you'll put
+this into your config file:
-* `require 'ripl/rc/strip_backtrace'`
+ require 'rib/core'
+ require 'rib/more/color'
- ripl prints the full backtrace upon exceptions, even the
- exceptions come from interactive environment, making it
- very verbose. This ripl plugin strips those backtrace.
+You can also write your plugins there. Here's another example:
-* `require 'ripl/rc/color'`
+ require 'rib/core'
+ Rib.config[:prompt] = '$ '
- There's ripl-color_result that make use of <a href="https://github.com/michaeldv/awesome_print">awesome_print</a>,
- <a href="http://coderay.rubychan.de/">coderay</a>, or <a href="https://github.com/janlelis/wirb">wirb</a>. The problem of awesome_print is it's too
- awesome and too verbose, and the problem of coderay and
- wirb is that they are both parser based. In ripl, this should
- be as simple as just print different colors upon different
- objects, instead of inspecting it and parsing it.
+ module RibPP
+ include Rib::Plugin
+ Rib::Shell.use(self)
- ripl/rc/color just uses a hash with Class to color mapping
- to pick up which color should be used upon a ruby object.
+ def format_result result
+ require 'pp'
+ result_prompt + result.pretty_inspect
+ end
+ end
- To customize the color schema, inspect `Ripl.config[:rc_color]`
+So that we override the original behaviour to pretty_inspect the result. You
+can also build your own gem and then simply require it in your config file.
-upon input:
+### As a debugging/interacting tool
-* `require 'ripl/rc/multiline'`
+Rib could be used as a kind of debugging tool which you can set break point
+in the source program.
- I need some modification on ripl-multi_line to make prompt
- work better, but not sure if I can come up a good fix and
- try to convince the author to accept those patches. So I
- just bundle and maintain it on my own. If you're using
- ripl-rc, you could use this plugin, otherwise, keep using
- ripl-multi_line.
+ require 'rib/rc' # This would load your ~/.config/rib/config.rb
+ require 'rib/anchor' # If you enabled this in config, then not needed.
+ Rib.anchor binding # This would give you an interactive shell
+ # when your program has been executed here.
-* `require 'ripl/rc/eat_whites'`
+ # But this might be called in a loop, you might only want to
+ # enter the shell under certain circumstance, then you'll need:
- irb will just give you another prompt upon an empty input,
- while ripl would show you that your input is nil. I don't like
- this, because sometimes I'll keep hitting enter to separate
- between inspects. This plugin would skip inspect if the input
- is empty just like irb.
+ require 'rib/debug'
+ Rib.enable_anchor do
+ # Only `Rib.anchor` called in the block would launch a shell
+ end
-special tool:
+ Rib.anchor binding # No effect (no-op) outside the block
-* `require 'ripl/rc/anchor'`
+Edit in place
- So this is my attempt to emulate pry in ripl. Instead
- trying to make pry support irb_history, colorizing, etc.,
- I think implement pry like feature in ripl is a lot easier.
- No need to be fancy, I just need the basic functionality.
+### As a shell framework
- To use it, use:
- <pre><code>Ripl.anchor your_object_want_to_be_viewed_as_self</code></pre>
- or
- <pre><code>Ripl.anchor binding</code></pre>
- in your code. Other than pry ripl support, you might be
- interested in <a href="https://github.com/cldwalker/ripl-rails">ripl-rails</a> and <a href="https://github.com/cldwalker/ripl-hijack">ripl-hijack</a>, too.
+The essence is:
-about config:
+ require 'rib'
-* `require 'ripl/rc/noirbrc'`
+All others are optional. The core plugins are lying in `rib/core/*.rb`,
+and more plugins are lying in `rib/more/*.rb`. There are also so-called
+zore plugins which are lying in `rib/zore/*.rb`, which are used as special
+Rib command, such as `Rib.anchor` and `Rib.edit`. You can simply get
- By default ripl is reading `~/.irbrc`. I don't think this
- is what people still using irb would want, because the
- configuration is totally different. This suppress that,
- make it only read `~/.riplrc`
+* All
+* App
-for lazies:
+Another one is local binding inside a method:
-* `require 'ripl/rc'`
+ Ripl.anchor binding
- This requires anything above for you, and is what `ripl rc`
- and `ripl rc rails` shell commands did.
+Then you can look through local variables inside a method
+with an interactive environment. Anchor could be nested, too.
+You can anchor another object inside a Rib session. The number
+shown in prompt is the level of anchors, starting from 1.
## LICENSE:
View
6 TODO
@@ -1,6 +0,0 @@
-= ripl-rc todo list
-
-* tests for each plugin
-* doc
-
-* read multiline histroy in irb_history
View
9 TODO.md
@@ -0,0 +1,9 @@
+# Rib TODO
+
+* Automatically generate (n-1)^2 tests for each plugin where n
+ is the number of plugins. This would test all the *combination* of
+ plugins usage, but not for *permutations*.
+* Runner tests
+* Multiline tests
+* More and more tests
+* Documentation
View
25 rib.gemspec
@@ -7,7 +7,16 @@ Gem::Specification.new do |s|
s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
s.authors = [%q{Lin Jen-Shin (godfat)}]
s.date = %q{2011-08-08}
- s.description = %q{ripl plugins collection, take you want, leave you don't.}
+ s.description = %q{Ruby-Interactive-ruBy -- Yet another interactive Ruby shell
+
+Rib is based on the design of [ripl][] and the work of [ripl-rc][], some of
+the features are also inspired by [pry][]. The aim of Rib is to be fully
+featured and yet very easy to opt-out or opt-in other features. It shall
+be simple, lightweight and modular so that everyone could customize Rib.
+
+[ripl]: https://github.com/cldwalker/ripl
+[ripl-rc]: https://github.com/godfat/ripl-rc
+[pry]: https://github.com/pry/pry}
s.email = [%q{godfat (XD) godfat.org}]
s.executables = [
%q{rib},
@@ -16,24 +25,23 @@ Gem::Specification.new do |s|
%q{rib-rails},
%q{rib-ramaze}]
s.extra_rdoc_files = [
- %q{CHANGES},
%q{CONTRIBUTORS},
%q{LICENSE},
- %q{TODO}]
+ %q{CHANGES.md},
+ %q{TODO.md},
+ %q{CONTRIBUTORS}]
s.files = [
%q{.gitignore},
%q{.gitmodules},
%q{.travis.yml},
- %q{2011-02-28.md},
- %q{CHANGES},
+ %q{CHANGES.md},
%q{CONTRIBUTORS},
- %q{EXAMPLE.md},
%q{Gemfile},
%q{LICENSE},
%q{README},
%q{README.md},
%q{Rakefile},
- %q{TODO},
+ %q{TODO.md},
%q{bin/rib},
%q{bin/rib-all},
%q{bin/rib-auto},
@@ -69,7 +77,6 @@ Gem::Specification.new do |s|
%q{lib/rib/zore/anchor.rb},
%q{lib/rib/zore/edit.rb},
%q{rib.gemspec},
- %q{screenshot.png},
%q{task/.gitignore},
%q{task/gemgem.rb},
%q{test/core/test_completion.rb},
@@ -87,7 +94,7 @@ Gem::Specification.new do |s|
%q{README}]
s.require_paths = [%q{lib}]
s.rubygems_version = %q{1.8.7}
- s.summary = %q{ripl plugins collection, take you want, leave you don't.}
+ s.summary = %q{Ruby-Interactive-ruBy -- Yet another interactive Ruby shell}
s.test_files = [
%q{test/core/test_completion.rb},
%q{test/core/test_history.rb},
View
BIN screenshot.png
Deleted file not rendered

0 comments on commit b928849

Please sign in to comment.
Something went wrong with that request. Please try again.