ttycoke 0.2.0

data/.gitignore

@@ -0,0 +1,16 @@
+## EMACS
+*~
+\#*
+.\#*
+
+## VIM
+*.swp
+
+## PROJECT::SPECIFIC
+TAGS
+*.log
+*.gem
+.bundle
+Gemfile.lock
+pkg
+.yardoc

data/.togglerc

@@ -0,0 +1,10 @@
+;; -*- mode: emacs-lisp; -*-
+
+(add-to-list
+ 'toggle-mapping-styles
+ '(ttycoke
+   ("test/ttycoke/test_\\1.rb" . "lib/ttycoke/\\1.rb")
+   ("test/test_\\1.rb" . "lib/\\1.rb")
+   ("test_\\1.rb"      . "\\1.rb")))
+
+(buffer-toggle-style 'ttycoke)

data/.tork.rb

@@ -0,0 +1,2 @@
+# -*- encoding: utf-8 -*-
+require 'tork/config/logdir'

data/.travis.yml

@@ -0,0 +1,6 @@
+rvm:
+  - 1.9.3
+  - 1.9.2
+  - rbx
+
+script: "rake"

data/LICENSE

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) 2012 Jose Pablo Barrantes
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,150 @@
+# TTYCoke [![Build Status](https://secure.travis-ci.org/jpablobr/ttycoke.png?branch=master)][travis]
+
+[travis]: http://travis-ci.org/jpablobr/ttycoke
+
+TTYCoke lets one modify the colorset of a running program (that
+display output to the command-line) based on predefined regular
+expression. Basically it's wrapper around the program, executing it
+and parsing its stdout stream (where it will apply the matching
+rules/colors).
+
+## <a name="Before-After"></a>Before/After
+
+[![before](http://i.imgur.com/nIen0.png)][before] [![after](http://i.imgur.com/4iVkc.png)][after]
+
+[before]: http://i.imgur.com/nIen0.png
+[after]: http://i.imgur.com/4iVkc.png
+
+Initial disclaimer! This mess is raw, like sushi. So, haters to the left.
+
+anyway, 
+
+## <a name="Installation"></a>Installation :)
+
+For specific Ruby version requirements, see the [Travis build](http://travis-ci.org/#!/jpablobr/ttycoke). ATM > 1.9.
+
+With RubyGems, simply open a terminal and type:
+
+    $ {sudo} gem install ttycoke
+
+Local installation:
+
+[Download](http://github.com/jpablobr/ttycoke/download) the tarball package and:
+
+    $ tar -xvzf ttycoke-{version}.tgz
+
+or
+
+    $ git clone https://github.com/jpablobr/ttycoke.git
+
+then 
+
+    $ cd ttycoke-{version}
+    $ {sudo} rake install
+
+Now you are ready to start coking! 
+
+## <a name="Usage"></a>Usage
+
+    $ ttycoke {program-name}
+
+If the program exist in the config file, it will use its rules to `ttycoke`
+it, otherwise it will fallback to its normal execution.
+
+You can also define your own rules for things such as `tailing` your logs! Something like the following should work:
+
+Create an executable shell script and name it lets say, `my_awesome_app_logs.sh` with:
+
+    #!/bin/sh
+    tail -f ~/apps/my_awesome_app/log/**/*.log
+
+Then in your terminal you can `ttycoke` it as such:
+
+    $ ttycoke my_awesome_app_logs.sh # <3<3<3
+
+if you were creative enough, you'll be seeing rainbows! 
+
+Again, it's just a wrapper around the program, It just parses it
+stdout stream, so its capable of much more!
+
+## <a name="Configuration"></a>Configuration
+The following rake task will copy the `ttycoke/config/config.yaml` file to your `$HOME` directory as `.ttycokerc`. 
+
+    $ rake setup 
+
+This file contains the regular expression rules and it's also where you'll be adding yours!
+
+## <a name="How-it-works"></a>How it works
+
+Basically it's just 1:1 match to the specified colors in the regular
+expression groups. So for example, with the following rule:
+
+``` yaml
+    lsmod:
+      regex: !ruby/regexp 
+        /^(?<green>\w+)(?<uncolored>\s+)(?<blue>\d+)(?<uncolored>\s+)(?<yellow>\d+)(?<magenta>.+)/
+
+```
+
+the lsmod program will be matched as follows: (I know kind of obvious)
+
+    '/^(?<green>\w+)(?<uncolored>\s+)(?<blue>\d+)(?<uncolored>\s+)(?<yellow>\d+)(?<magenta>.+)/'
+        |            |                |           |                |             |
+        |            |                |           |                |             \_: magenta
+        |            |                |           |                \_: yellow
+        |            |                |           \_: uncolored
+        |            |                \_:blue
+        |            \_:uncolored
+        \_:green
+
+Based on that you can now take it a bit further and for example the
+following will create a green/red TDD kind of output:
+
+     ((?<green>success)|(?<red>fail|error))
+
+The first screenshot is based of the following:
+
+``` yaml
+tail_tork_logs:
+  -
+    results:
+      regex: !ruby/regexp 
+        /^(?<underscore>Finished.*)/
+    error:
+      regex: !ruby/regexp 
+        /(?<red>.+(Error|Failure):)/
+    expected:
+      regex: !ruby/regexp 
+        /(?<blue>--- expected)/
+    expected-string:
+      regex: !ruby/regexp 
+        /(?<blue>-\".+)/
+    actual:
+      regex: !ruby/regexp 
+        /(?<red>\++ actual)/
+    actual-string:
+      regex: !ruby/regexp 
+        /(?<red>\+\".+)/
+    at:
+      regex: !ruby/regexp 
+        /(?<on_yellow>@.+)/
+    stats:
+      regex: !ruby/regexp 
+        /(?<white>\d+ tests, )(?<green>\d+ assertions, )(?<magenta>\d+ failures, )(?<red>\d+ errors, )(?<yellow>\d+ skips)/
+```
+
+and the `tail_tork_logs` looks like this:
+
+    #!/bin/sh
+
+    tail -f log/test/**/*.log
+
+That's just from `tailing` the ouput of the [Tork](https://github.com/sunaku/tork) continuous testing framework.
+
+## <a name="todo"></a>TODO
+* Add more sample regular expression parsers.
+
+## <a name="copyright"></a>Copyright
+Copyright (c) 2012 Jose Pablo Barrantes. See [LICENSE][] for details.
+
+[license]: https://github.com/jpablobr/ttycoke/blob/master/LICENSE

data/Rakefile

@@ -0,0 +1,25 @@
+require 'rake'
+require 'rake/testtask'
+require 'bundler/gem_tasks'
+
+namespace :test do
+  Rake::TestTask.new do |t|
+    t.name = "minitest"
+    t.libs << "test"
+    t.test_files = FileList['test/ttycoke/test_*.rb', 'test/test_*.rb']
+    t.verbose = true
+  end
+end
+
+desc "install the rc file into user's home directory"
+task :setup do
+  if File.exist?(File.join(ENV['HOME'], ".ttycokerc"))
+    puts "#{File.join(ENV['HOME'], '.ttycokerc')} already exist."
+  else
+    puts "Coping .ttycokerc to $HOME directory"
+    system %Q{cp "$PWD/config/config.yaml" "$HOME/.ttycokerc"}
+    puts "done."
+  end
+end
+
+task :default => "test:minitest"

data/bin/ttycoke

@@ -0,0 +1,10 @@
+#!/usr/bin/env ruby -w
+
+require 'ttycoke'
+include TTYCoke::Log
+
+# Stdout/stderr should not buffer output
+$stdout.sync = true
+$stderr.sync = true
+
+TTYCoke::CLI.new.parse_options(ARGV)

data/config/config.yaml

@@ -0,0 +1,5 @@
+# This file imports all the rules from the ttycoke.d directory.
+import:
+  - /ttycoke.d/lsmod.yaml
+  - /ttycoke.d/id.yaml
+  - /ttycoke.d/tail_tork_logs.yaml

data/config/ttycoke.d/id.yaml

@@ -0,0 +1,4 @@
+id:
+  clrs: 
+  regex: !ruby/regexp 
+    /(?<green>\w+=)(?<yellow>\d+)/

data/config/ttycoke.d/lsmod.yaml

@@ -0,0 +1,3 @@
+lsmod:
+  regex: !ruby/regexp
+    /^(?<green>\w+)(?<uncolored>\s+)(?<blue>\d+)(?<uncolored>\s+)(?<yellow>\d+)(?<red>.+)/

data/config/ttycoke.d/tail_focus.yaml

@@ -0,0 +1,14 @@
+tail-focus.sh:
+  -
+    first:
+      regex: !ruby/regexp
+        /(?<red># \w+)/
+    second:
+      regex: !ruby/regexp
+        /(?<yellow>## \w+)/
+    third:
+      regex: !ruby/regexp
+        /(?<green>### \w+)/
+    fouth:
+      regex: !ruby/regexp
+        /(?<blue>#### \w+)/

data/config/ttycoke.d/tail_tork_logs.yaml

@@ -0,0 +1,26 @@
+tail_tork_logs:
+  -
+    results:
+      regex: !ruby/regexp 
+        /^(?<underscore>Finished.*)/
+    error:
+      regex: !ruby/regexp 
+        /(?<red>.+(Error|Failure):)/
+    expected:
+      regex: !ruby/regexp 
+        /(?<blue>--- expected)/
+    expected-string:
+      regex: !ruby/regexp 
+        /(?<blue>-\".+)/
+    actual:
+      regex: !ruby/regexp 
+        /(?<red>\++ actual)/
+    actual-string:
+      regex: !ruby/regexp 
+        /(?<red>\+\".+)/
+    at:
+      regex: !ruby/regexp 
+        /(?<on_yellow>@.+)/
+    stats:
+      regex: !ruby/regexp 
+        /(?<white>\d+ tests, )(?<green>\d+ assertions, )(?<magenta>\d+ failures, )(?<red>\d+ errors, )(?<yellow>\d+ skips)/

data/config/ttycoke.d/top.yaml

@@ -0,0 +1,8 @@
+top:
+  -
+    tasks: 
+      regex: !ruby/regexp 
+        /(?<green>Tasks:.*)/
+    tasks: 
+      regex: !ruby/regexp 
+        /(?<blue>CPU.*)/