kaboom 0.3.1 → 0.3.2

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    kaboom (0.3.1)
+    kaboom (0.3.2)
       json_pure (~> 1.5.3)
       multi_json (~> 1.0.3)
 

data/README.markdown

@@ -53,22 +53,9 @@ each others command lines
 
 ## Contribute
 
-Want to join the [Pantheon of
-Boom'ers](https://github.com/holman/boom/contributors)? I'd love to include
-your contributions, friend.
-
 Clone this repository, then run `bundle install`. That'll install all the gem
-dependencies. Make sure your methods are [TomDoc](http://tomdoc.org)'d
-properly, that existing tests pass (`rake`), and that any new functionality
+dependencies. Make sure that existing tests pass (`rake`), and that any new functionality
 includes appropriate tests. Bonus points if you're not updating the gemspec or
 bumping boom's version.
 
-All good? Cool! Then [send me a pull request](https://github.com/holman/boom/pull/new/master)!
-
-## I love you
-
-[Zach Holman](http://zachholman.com) made this. Ping me on Twitter —
-[@holman](http://twitter.com/holman) — if you're having issues, want me to
-merge in your pull request, or are using boom in a cool way. I'm kind of hoping
-this is generic enough that people do some fun things with it. First one to use
-`boom` to calculate their tax liability wins.
+All good? Cool! Then send me a pull request

data/bin/boom

@@ -3,6 +3,6 @@
 
 $:.unshift File.join(File.dirname(__FILE__), *%w[.. lib])
 
-require 'boom'
+require 'kaboom'
 
 Boom::Command.execute(*ARGV)

data/bin/kaboom

@@ -3,6 +3,6 @@
 
 $:.unshift File.join(File.dirname(__FILE__), *%w[.. lib])
 
-require 'boom'
+require 'kaboom'
 args = %w{remote} + ARGV
 Boom::Command.execute(*args)

data/kaboom.gemspec

@@ -13,20 +13,57 @@ Gem::Specification.new do |s|
   ## If your rubyforge_project name is different, then edit it and comment out
   ## the sub! line in the Rakefile
   s.name              = 'kaboom'
-  s.version           = '0.3.1'
+  s.version           = '0.3.2'
   s.date              = '2012-03-17'
   s.rubyforge_project = 'boom'
 
   ## Make sure your summary is short. The description may be as long
   ## as you like.
-  s.summary     = "boom lets you access text snippets over your command line."
-  s.description = "God it's about every day where I think to myself, gadzooks,
+  s.summary     = "kaboom for accessing/share text snippets on the command line"
+
+  s.description = "This is a fork of Zach Holman's amazing boom. Explanation for
+  the fork follows Zach's intro to boom:
+
+  God it's about every day where I think to myself, gadzooks,
   I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if
   I had something like boom to store all these commonly-used text snippets for
   me? Then I realized that was a worthless idea since boom hadn't been created
   yet and I had no idea what that statement meant. At some point I found the
   code for boom in a dark alleyway and released it under my own name because I
-  wanted to look smart."
+  wanted to look smart.
+
+  Explanation for my fork:
+
+  Zach didn't fancy changing boom a great deal to handle the case of remote and
+  local boom repos. Which is fair enough I believe in simplicity.
+  But I also believe in getting tools to do what you want them to do.
+  So with boom, you can change your storage with a 'boom storage' command, but
+  that's a hassle when you want to share stuff.
+
+  So kaboom does what boom does plus simplifies maintaining two boom repos.
+  What this means is that you can pipe input between remote and local boom
+  instances. My use case is to have a redis server in our office and be able
+  to share snippets between each other, but to also be able to have personal
+  repos.
+
+  It's basically something like distributed key-value stores. I imagine some of
+  the things that might be worth thinking about, based on DVC are:
+
+  Imports/Exports of lists/keys/values between repos.
+  Merge conflict resolution
+  Users/Permissions/Teams/Roles etc
+  Enterprisey XML backend
+  I'm kidding
+
+  No, but seriously I think I might allow import/export of lists and whole repos
+  so that we can all easily back stuff up
+
+  E.g.
+  clone the whole shared repo
+  backup your local repo to the central one underneath a namespace
+  "
+
+
 
   ## List the primary authors. If there are a bunch of authors, it's probably
   ## better to set the email to an email list or something. If you don't have
@@ -80,6 +117,7 @@ Gem::Specification.new do |s|
     completion/boom.zsh
     kaboom.gemspec
     lib/kaboom.rb
+    lib/kaboom/.command.rb.swo
     lib/kaboom/color.rb
     lib/kaboom/command.rb
     lib/kaboom/config.rb

data/lib/kaboom.rb

@@ -30,7 +30,7 @@ require 'kaboom/core_ext/symbol'
 require 'kaboom/remote'
 
 module Boom
-  VERSION = '0.3.1'
+  VERSION = '0.3.2'
 
   extend self
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: kaboom
 version: !ruby/object:Gem::Version
-  version: 0.3.1
+  version: 0.3.2
   prerelease: 
 platform: ruby
 authors:
@@ -14,7 +14,7 @@ date: 2012-03-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: multi_json
-  requirement: &70094413093860 !ruby/object:Gem::Requirement
+  requirement: &70316779273620 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -22,10 +22,10 @@ dependencies:
         version: 1.0.3
   type: :runtime
   prerelease: false
-  version_requirements: *70094413093860
+  version_requirements: *70316779273620
 - !ruby/object:Gem::Dependency
   name: json_pure
-  requirement: &70094413093400 !ruby/object:Gem::Requirement
+  requirement: &70316779273160 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -33,10 +33,10 @@ dependencies:
         version: 1.5.3
   type: :runtime
   prerelease: false
-  version_requirements: *70094413093400
+  version_requirements: *70316779273160
 - !ruby/object:Gem::Dependency
   name: mocha
-  requirement: &70094413092800 !ruby/object:Gem::Requirement
+  requirement: &70316779272700 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -44,10 +44,10 @@ dependencies:
         version: 0.9.9
   type: :development
   prerelease: false
-  version_requirements: *70094413092800
+  version_requirements: *70316779272700
 - !ruby/object:Gem::Dependency
   name: rake
-  requirement: &70094413092140 !ruby/object:Gem::Requirement
+  requirement: &70316779272240 !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ~>
@@ -55,14 +55,30 @@ dependencies:
         version: 0.9.2
   type: :development
   prerelease: false
-  version_requirements: *70094413092140
-description: ! "God it's about every day where I think to myself, gadzooks,\n  I keep
-  typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if\n  I had
-  something like boom to store all these commonly-used text snippets for\n  me? Then
-  I realized that was a worthless idea since boom hadn't been created\n  yet and I
-  had no idea what that statement meant. At some point I found the\n  code for boom
-  in a dark alleyway and released it under my own name because I\n  wanted to look
-  smart."
+  version_requirements: *70316779272240
+description: ! "This is a fork of Zach Holman's amazing boom. Explanation for\n  the
+  fork follows Zach's intro to boom:\n\n  God it's about every day where I think to
+  myself, gadzooks,\n  I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't
+  it be great if\n  I had something like boom to store all these commonly-used text
+  snippets for\n  me? Then I realized that was a worthless idea since boom hadn't
+  been created\n  yet and I had no idea what that statement meant. At some point I
+  found the\n  code for boom in a dark alleyway and released it under my own name
+  because I\n  wanted to look smart.\n\n  Explanation for my fork:\n\n  Zach didn't
+  fancy changing boom a great deal to handle the case of remote and\n  local boom
+  repos. Which is fair enough I believe in simplicity.\n  But I also believe in getting
+  tools to do what you want them to do.\n  So with boom, you can change your storage
+  with a 'boom storage' command, but\n  that's a hassle when you want to share stuff.\n\n
+  \ So kaboom does what boom does plus simplifies maintaining two boom repos.\n  What
+  this means is that you can pipe input between remote and local boom\n  instances.
+  My use case is to have a redis server in our office and be able\n  to share snippets
+  between each other, but to also be able to have personal\n  repos.\n\n  It's basically
+  something like distributed key-value stores. I imagine some of\n  the things that
+  might be worth thinking about, based on DVC are:\n\n  Imports/Exports of lists/keys/values
+  between repos.\n  Merge conflict resolution\n  Users/Permissions/Teams/Roles etc\n
+  \ Enterprisey XML backend\n  I'm kidding\n\n  No, but seriously I think I might
+  allow import/export of lists and whole repos\n  so that we can all easily back stuff
+  up\n\n  E.g.\n  clone the whole shared repo\n  backup your local repo to the central
+  one underneath a namespace\n  "
 email: markthedeveloper@gmail.com
 executables:
 - boom
@@ -85,6 +101,7 @@ files:
 - completion/boom.zsh
 - kaboom.gemspec
 - lib/kaboom.rb
+- lib/kaboom/.command.rb.swo
 - lib/kaboom/color.rb
 - lib/kaboom/command.rb
 - lib/kaboom/config.rb
@@ -128,7 +145,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: 3545507400932762145
+      hash: -4015829161079492455
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
@@ -140,7 +157,7 @@ rubyforge_project: boom
 rubygems_version: 1.8.17
 signing_key: 
 specification_version: 2
-summary: boom lets you access text snippets over your command line.
+summary: kaboom for accessing/share text snippets on the command line
 test_files:
 - test/test_color.rb
 - test/test_command.rb