hirohig_palindrome 0.1.0

data/vendor/bundle/ruby/2.6.0/gems/ansi-1.5.0/DEMO.md

@@ -0,0 +1,451 @@
+# ANSI::Code
+
+Require the library.
+
+    require 'ansi/code'
+
+ANSI::Code can be used as a functions module.
+
+    str = ANSI::Code.red + "Hello" + ANSI::Code.blue + "World"
+    str.assert == "\e[31mHello\e[34mWorld"
+
+If a block is supplied to each method then yielded value will
+be wrapped in the ANSI code and clear code. 
+
+    str = ANSI::Code.red{ "Hello" } + ANSI::Code.blue{ "World" }
+    str.assert == "\e[31mHello\e[0m\e[34mWorld\e[0m"
+
+More conveniently the ANSI::Code module extends ANSI itself.
+
+    str = ANSI.red + "Hello" + ANSI.blue + "World"
+    str.assert == "\e[31mHello\e[34mWorld"
+
+    str = ANSI.red{ "Hello" } + ANSI.blue{ "World" }
+    str.assert == "\e[31mHello\e[0m\e[34mWorld\e[0m"
+
+In the appropriate context the ANSI::Code module can also be
+included, making its methods directly accessible.
+
+    include ANSI::Code
+
+    str = red + "Hello" + blue + "World"
+    str.assert == "\e[31mHello\e[34mWorld"
+
+    str = red{ "Hello" } + blue{ "World" }
+    str.assert == "\e[31mHello\e[0m\e[34mWorld\e[0m"
+
+Along with the single font colors, the library include background colors.
+
+    str = on_red + "Hello"
+    str.assert == "\e[41mHello"
+
+As well as combined color methods.
+
+    str = white_on_red + "Hello"
+    str.assert == "\e[37m\e[41mHello"
+
+The ANSI::Code module supports most standard ANSI codes, though
+not all platforms support every code, so YMMV.
+
+
+# String Extensions
+
+In addition the library offers an extension to String class
+called #ansi, which allows some of the ANSI::Code methods
+to be called in a more object-oriented fashion.
+
+    require 'ansi/core'
+
+    str = "Hello".ansi(:red) + "World".ansi(:blue)
+    str.assert == "\e[31mHello\e[0m\e[34mWorld\e[0m"
+
+
+# ANSI::Logger
+
+Require the ANSI::Logger library.
+
+    require 'ansi/logger'
+
+Create a new ANSI::Logger
+
+    log = ANSI::Logger.new(STDOUT)
+
+Info logging appears normal.
+
+    log.info{"Info logs are green.\n"}
+
+Warn logging appears yellow.
+
+    log.warn{"Warn logs are yellow.\n"}
+
+Debug logging appears cyan.
+
+    log.debug{"Debug logs are cyan.\n"}
+
+Error logging appears red.
+
+    log.error{"Error logs are red.\n"}
+
+Fatal logging appears bright red.
+
+    log.fatal{"Fatal logs are bold red!\n"}
+
+
+# ANSI::Progressbar
+
+Pretty progress bars are easy to construct.
+
+    require 'ansi/progressbar'
+
+    pbar = ANSI::Progressbar.new("Test Bar", 100)
+
+Running the bar simply requires calling the #inc method during
+a loop and calling #finish when done.
+
+    100.times do |i|
+      sleep 0.01
+      pbar.inc
+    end
+    pbar.finish
+
+We will use this same rountine in all the examples below, so lets
+make a quick macro for it. Notice we have to use #reset first
+before reusing the same progress bar.
+
+    def run(pbar)
+      pbar.reset
+      100.times do |i|
+        sleep 0.01
+        pbar.inc
+      end
+      pbar.finish
+      puts
+    end
+
+The progress bar can be stylized in almost any way.
+The #format setter provides control over the parts
+that appear on the line. For example, by default the
+format is:
+
+    pbar.format("%-14s %3d%% %s %s", :title, :percentage, :bar, :stat)
+
+So lets vary it up to demonstrate the case.
+
+    pbar.format("%-14s %3d%% %s %s", :title, :percentage, :stat, :bar)
+    run(pbar)
+
+The progress bar has an extra build in format intended for use with
+file downloads called #transer_mode.
+
+    pbar.transfer_mode
+    run(pbar)
+
+Calling this methods is the same as calling:
+
+    pbar.format("%-14s %3d%% %s %s",:title, :percentage, :bar, :stat_for_file_transfer)
+    run(pbar)
+
+The #style setter allows each part of the line be modified with ANSI codes. And the
+#bar_mark writer can be used to change the character used to make the bar.
+
+    pbar.standard_mode
+    pbar.style(:title => [:red], :bar=>[:blue])
+    pbar.bar_mark = "="
+    run(pbar)
+
+
+# ANSI::Mixin
+
+The ANSI::Mixin module is design for including into
+String-like classes. It will support any class that defines
+a #to_s method.
+
+    require 'ansi/mixin'
+
+In this demonstration we will simply include it in the
+core String class.
+
+    class ::String
+      include ANSI::Mixin
+    end
+
+Now all strings will have access to ANSI's style and color
+codes via simple method calls.
+
+    "roses".red.assert == "\e[31mroses\e[0m"
+
+    "violets".blue.assert == "\e[34mviolets\e[0m"
+
+    "sugar".italic.assert == "\e[3msugar\e[0m"
+
+The method can be combined, of course.
+
+    "you".italic.bold.assert == "\e[1m\e[3myou\e[0m\e[0m"
+
+The mixin also supports background methods.
+
+    "envy".on_green.assert == "\e[42menvy\e[0m"
+
+And it also supports the combined foreground-on-background 
+methods.
+
+    "b&w".white_on_black.assert == "\e[37m\e[40mb&w\e[0m"
+
+
+# ANSI::String
+
+The ANSI::String class is a very sophisticated implementation
+of Ruby's standard String class, but one that can handle
+ANSI codes seamlessly.
+
+    require 'ansi/string'
+
+    flower1 = ANSI::String.new("Roses")
+    flower2 = ANSI::String.new("Violets")
+
+Like any other string.
+
+    flower1.to_s.assert == "Roses"
+    flower2.to_s.assert == "Violets"
+
+Bet now we can add color.
+
+    flower1.red!
+    flower2.blue!
+
+    flower1.to_s.assert == "\e[31mRoses\e[0m"
+    flower2.to_s.assert == "\e[34mViolets\e[0m"
+
+Despite that the string representation now contains ANSI codes,
+we can still manipulate the string in much the same way that
+we manipulate an ordinary string.
+
+    flower1.size.assert == 5
+    flower2.size.assert == 7
+
+Like ordinary strings we can concatenate the two strings
+
+    flowers = flower1 + ' ' + flower2
+    flowers.to_s.assert == "\e[31mRoses\e[0m \e[34mViolets\e[0m"
+
+    flowers.size.assert == 13
+
+Standard case conversion such as #upcase and #downcase work.
+
+    flower1.upcase.to_s.assert == "\e[31mROSES\e[0m"
+    flower1.downcase.to_s.assert == "\e[31mroses\e[0m"
+
+Some of the most difficult methods to re-implement were the 
+substitution methods such as #sub and #gsub. They are still
+somewhat more limited than the original string methods, but
+their primary functionality should work.
+
+    flower1.gsub('s', 'z').to_s.assert == "\e[31mRozez\e[0m"
+
+There are still a number of methods that need implementation.
+ANSI::String is currently a very partial implementation. But
+as you can see from the methods it does currently support,
+is it already useful.
+
+
+# ANSI::Columns
+
+The +Columns+ class makes it easy to create nice looking text columns,
+sorted from top to bottom, right to left (as opposed to the other way
+around).
+
+    require 'ansi/columns'
+
+    list = %w{a b c d e f g h i j k l}
+
+    columns = ANSI::Columns.new(list)
+
+    columns.to_s(4)
+
+The output will be:
+
+    a d g j
+    b e h k
+    c f i l
+
+Besides an array of elements, Columns.new can take a string in which
+the elements are divided by newlines characters. The default column
+size can also be given to the initializer.
+
+    list = "a\nb\nc\nd\ne\nf\ng\nh\ni\nj\nk\nl"
+
+    columns = ANSI::Columns.new(list, :columns=>6)
+
+    columns.to_s
+
+The output will be:
+
+    a c e g i k
+    b d f h j l
+
+If the column count is +nil+, then the number of columns will be calculated
+as a best fit for the current terminal window.
+
+## Padding
+
+Columns can adjust the padding between cells.
+
+    list = %w{a b c d e f g h i j k l}
+
+    columns = ANSI::Columns.new(list, :padding=>2)
+
+    columns.to_s(4)
+
+The output will be:
+
+    a  d  g  j
+    b  e  h  k
+    c  f  i  l
+
+## Alignment
+
+Columns can also be aligned either left or right.
+
+    list = %w{xx xx xx yy y yy z zz z}
+
+    columns = ANSI::Columns.new(list, :align=>:right)
+
+    columns.to_s(3)
+
+The output will be:
+
+    xx yy  z
+    xx  y zz
+    xx yy  z
+
+## Format
+
+Lastly, columns can be augmented with ANSI codes. This is done through
+a formatting block. The block can take up to three parameters, the cell
+content, the column and row numbers, or the cell and the column and row
+numbers.
+
+    list = %w{a b c d e f g h i j k l}
+
+    columns = ANSI::Columns.new(list){ |c,r| r % 2 == 0 ? :red : :blue }
+
+    out = columns.to_s(4)
+
+    out.assert == (
+      "\e[31ma \e[0m\e[31md \e[0m\e[31mg \e[0m\e[31mj \e[0m\n" +
+      "\e[34mb \e[0m\e[34me \e[0m\e[34mh \e[0m\e[34mk \e[0m\n" +
+      "\e[31mc \e[0m\e[31mf \e[0m\e[31mi \e[0m\e[31ml \e[0m\n"
+    )
+
+
+# ANSI::Table
+
+The ANSI::Table class can be used to output tabular data with nicely
+formated ASCII cell borders.
+
+    require 'ansi/table'
+
+The constructor takes an 2-dimensional array.
+
+    data = [
+      [ 10, 20, 30 ],
+      [ 20, 10, 20 ],
+      [ 50, 40, 20 ]
+    ]
+
+    table = ANSI::Table.new(data)
+
+    table.to_s
+
+The output will be:
+
+    +----+----+----+
+    | 10 | 20 | 30 |
+    | 20 | 10 | 20 |
+    | 50 | 40 | 20 |
+    +----+----+----+
+
+
+
+# ANSI::Diff
+
+    require 'ansi/diff'
+
+    a = 'abcYefg'
+    b = 'abcXefg'
+
+    diff = ANSI::Diff.new(a,b)
+
+    diff.to_s.assert == "\e[31mabc\e[0m\e[33mYefg\e[0m\n\e[31mabc\e[0mXefg"
+
+Try another.
+
+    a = 'abc'
+    b = 'abcdef'
+
+    diff = ANSI::Diff.new(a,b)
+
+    diff.to_s.assert == "\e[31mabc\e[0m\n\e[31mabc\e[0mdef"
+
+And another.
+
+    a = 'abcXXXghi'
+    b = 'abcdefghi'
+
+    diff = ANSI::Diff.new(a,b)
+
+    diff.to_s.assert == "\e[31mabc\e[0m\e[33mXXXghi\e[0m\n\e[31mabc\e[0mdefghi"
+
+And another.
+
+    a = 'abcXXXdefghi'
+    b = 'abcdefghi'
+
+    diff = ANSI::Diff.new(a,b)
+
+    diff.to_s.assert == "\e[31mabc\e[0m\e[33mXXX\e[0m\e[35mdefghi\e[0m\n\e[31mabc\e[0m\e[35mdefghi\e[0m"
+
+Comparison that is mostly different.
+
+    a = 'abcpppz123'
+    b = 'abcxyzzz43'
+
+    diff = ANSI::Diff.new(a,b)
+
+    diff.to_s.assert == "\e[31mabc\e[0m\e[33mpppz123\e[0m\n\e[31mabc\e[0mxyzzz43"
+
+
+# ANSI::BBCode
+
+The BBCode module provides methods for converting between
+BBCodes, basic HTML and ANSI codes.
+
+    require 'ansi/bbcode'
+
+BBCodes are color and style codes in square brackets, quite
+popular with on line forums.
+
+    bbcode = "this is [COLOR=red]red[/COLOR], this is [B]bold[/B]"
+
+We can convert this to ANSI code simply enough:
+
+    ansi = ANSI::BBCode.bbcode_to_ansi(bbcode)
+
+    ansi.assert == "this is \e[0;31mred\e[0m, this is \e[1mbold\e[0m\n"
+
+In addition the BBCode module supports conversion to simple HTML.
+
+    html = ANSI::BBCode.bbcode_to_html(bbcode)
+
+    html.assert == "this is <font color=\"red\">red</font>, this is <strong>bold</strong><br />\n"
+
+
+# ANSI::Terminal
+
+We should be ables to get the terminal width via the `terminal_width` method.
+
+    width = ANSI::Terminal.terminal_width
+
+    Fixnum.assert === width
+
+

data/vendor/bundle/ruby/2.6.0/gems/ansi-1.5.0/HISTORY.md

@@ -0,0 +1,217 @@
+# RELEASE HISTORY
+
+## 1.5.0 | 2015-01-16
+
+ANSI 1.5 introduces one change that is not backward compatiable. The 
+`:clear_line` code no longer clears to the end of the line. Instead it
+clears the entire line. If you have used this in the past you
+will need to update your code to use `:clear_eol` or `:clear_right`
+instead. In addition this release finally fixes some long time issues
+with Windows compatability, and a few other bugs. Yeah!
+
+Changes:
+
+* Alias `:right` and `:left` as `:forward` and `:back` respectively.
+* Change `:clear_line` to clear whole line, not just to the end of line.
+* Add `:cursor_hide` and `:cursor_show` codes.
+* Fix and adjust #rgb method to work as one would expect.
+* Fix Windows compatability (old code was alwasy using stty).
+* Fix duplicated hash key in chart.rb.
+
+
+## 1.4.3 | 2012-06-26
+
+This release bring two small changes. The first improves support
+for Windows by only rescuing LoadError when 'win32console' fails
+to load. The second improves the heuritstics used for determining
+the current terminal screen width.
+
+Changes:
+
+* Only rescue LoadError on windows require. (#9) [bug]
+* Improvements for getting proper screen width.
+
+
+## 1.4.2 | 2012-01-29
+
+ANSI chains are a new feature inspired by Kazuyoshi Tlacaelel's Isna project.
+It is a fluid notation for the String#ansi method, e.g. `"foo".red.on_white`.
+Also, ASNI now supports "smart codes", preventing previously applied codes
+from undermining the applicaiton of additional codes --a subtle issue that
+most other ANSI libraries overlook. Plus a few other improvements including
+that of the API documentation.
+
+Changes:
+
+* Add ANSI::Chains, extending String#ansi method.
+* Support smart code application.
+* Add Diff#to_a and shortcut to it via Diff.diff().
+* Improve #colorize method in ProgressBar.
+* Change ProgressBar's default mark to `|` instead of `o`.
+* Fix Curses return order of screen cols and rows.
+* Support center alignment in Columns.
+* Support custom padding for Columns.
+
+
+## 1.4.1 | 2011-11-09
+
+This release simply fixes a documentation issue, to make sure
+QED.rdoc appears in the YARD docs. And a shout-out to Chad Perrin
+for submitting some doc fixes for this project and a few other
+Rubyworks projects.
+
+Changes:
+
+* Adjust .yardopts file.
+* Documentation fixes.
+
+
+## 1.4.0 | 2011-11-05
+
+New release adds a HexDump class for colorized byte string dumps
+and fixes some minor cell size issues with the Table class.
+This release also modernizes the build config and changes the
+license to BSD-2-Clause.
+
+Changes:
+
+* Add HexDump class.
+* Fix cell size of tables when ANSI codes are used.
+* Fix extra ansi codes in tables without format.
+* Modernize build configuration.
+* Switch to BSD-2-Clause license.
+
+
+## 1.3.0 | 2011-06-30
+
+This release cleans up the Code module. It adds support for x-term
+256 color codes. Also, the Diff class is now awesome, making use of
+an LCS algorithm. But the most important difference with this release
+is that the String core extensions are in their own file, core.rb.
+If you want to use them you will need to require `ansi` or `ansi/core`.
+
+Changes:
+
+* Clean-up Code module.
+* Utilize common chart for Code methods.
+* Constants now have their own module.
+* Move core methods to `ansi/core.rb`.
+* Add XTerm 256 color code support.
+* Improved Diff class with LCS algorithm.
+
+
+## 1.2.5 | 2011-05-03
+
+This release introduces a preliminary rendition of a Diff class
+for getting colorized comparisons of strings and other objects.
+It's not officially supported yet, so this is only a point release.
+
+Changes:
+
+* Added Diff class for colorized comparisons.
+* Fixed minor issue with Columns format block; col comes before row.
+
+
+## 1.2.4 | 2011-04-29
+
+This release improves to the ANSI::Columns class. In particular the
+layout is more consistent with intended functionality.
+
+Changes:
+
+* Improved ANSI::Columns to give more consistent output.
+* ANSI::Columns#to_s can override number of columns.
+* ANSI::Columns can take a String or Array list.
+
+
+## 1.2.3 | 2011-04-08
+
+Minor release to add #clear method to ProgressBar and provide bug
+fix to BBCode.ansi_to_bbcode. Big thanks goes to Junegunn Choi 
+for this fix.
+
+Changes:
+
+* Add ProgressBar#clear method.
+* Fixed ANSI::BBCode.ansi_to_bbcode and ansi_to_html from omitting lines
+without any ansi code (Junegunn Choi).
+
+## 1.2.2 | 2010-06-12
+
+This release removes warnings about string arguments for certain
+ANSI::Code methods. While the string form is considered deprecated,
+for a few methods there is no use for any argument, so the string
+form can remain. In addition, String#unansi has been added to
+compliment String#ansi. Lastly, this release also adds the #display
+method to ANSI::Mixin.
+
+Changes:
+
+* Remove string argument warnings.
+* Add String#unansi and String#unansi!
+* Add ANSI::Mixin#display.
+
+
+## 1.2.1 | 2010-05-10
+
+This release was simply a quick fix to remove the incorrect embedded
+version number, until it gets fixed.
+
+
+## 1.2.0 | 2010-05-10
+
+This release entails numerous improvements. First and foremost
+the Code module is transitioning to a block interface only
+and phasing out the string argument interface. Admittedly this
+is mildly unconventional, but it allows the arguments to be used
+as options with common defaults more elegantly.
+
+Another important change is that ANSI::Code no longer provides
+String extension methods when included. For this use the new
+ANSI::Mixin.
+
+Other improvements include a String extension, #ansi, added to
+code.rb, which makes it even easier to apply ANSI codes to strings.
+Also, the ANSI::String class has been fixed (a few bugs crept
+it with the last release) and continues to improve. On top of all
+this testing has substantially improved thanks to QED.
+
+Changes:
+
+* Support string argument for now but with warning
+* Bug fixes for ANSI::String
+* Add mixin.rb for alternate mixin.
+* Many new tests and QED documents.
+
+
+## 1.1.0 | 2009-10-04
+
+This release is the first toward making the ANSI library
+more widely usable.
+
+Changes:
+
+* Add bbcode.rb for conversion between BBCode/ANSI/HTML.
+* ProgressBar and Progressbar are the same.
+* Other minor underthehood improvements.
+
+
+## 1.0.1 | 2009-08-15
+
+The release fixes a single bug that should allow Ruby 1.9
+to use the ANSI library.
+
+Changes:
+
+* Renamed PLATFORM to RUBY_PLATFORM
+
+
+## 1.0.0 | 2009-08-15
+
+This is the initial stand-alone release of ANSI, a collection
+of ANSI based classes spun-off from Ruby Facets.
+
+Changes:
+
+* Happy Birthday!
+

data/vendor/bundle/ruby/2.6.0/gems/ansi-1.5.0/LICENSE.txt

@@ -0,0 +1,23 @@
+BSD-2-Clause License (http://spdx.org/licenses/BSD-2-Clause)
+
+Redistribution and use in source and binary forms, with or without modification, are
+permitted provided that the following conditions are met:
+
+   1. Redistributions of source code must retain the above copyright notice, this list of
+      conditions and the following disclaimer.
+
+   2. Redistributions in binary form must reproduce the above copyright notice, this list
+      of conditions and the following disclaimer in the documentation and/or other materials
+      provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ``AS IS'' AND ANY EXPRESS OR IMPLIED
+WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS
+OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
+ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+