rib 0.0.1 → 0.1.0

data/.gitignore

@@ -0,0 +1,6 @@
+pkg
+rdoc
+*.rbc
+.bundle
+.yardoc
+Gemfile.lock

data/.gitmodules

@@ -0,0 +1,3 @@
+[submodule "task"]
+	path = task
+	url = git://github.com/godfat/gemgem.git

data/.travis.yml

@@ -0,0 +1,9 @@
+script: 'git submodule update --init; bundle exec rake test'
+rvm:
+  - 1.8.7
+  - 1.9.2
+  - ruby-head
+  - rbx
+  - rbx-2.0
+  - jruby
+  - ree

data/2011-02-28.md

@@ -0,0 +1,203 @@
+[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)

data/CHANGES

@@ -0,0 +1,86 @@
+= 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

data/CONTRIBUTORS

@@ -0,0 +1,2 @@
+Lin Jen-Shin (godfat)
+miaout17 (miaout17)

data/Gemfile

@@ -0,0 +1,4 @@
+
+source 'http://rubygems.org'
+
+gemspec

data/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.