tomkersten-vixploder 0.1.3 → 0.1.4

data/History.txt

@@ -1,3 +1,10 @@
+== 0.1.4 2009-01-13
+
+* Removed auto-folding
+* Updated README.txt (why was the description so long)
+* Officially included a couple scripts for testing 256-color soupport in your terminal (256colors2.pl, colortest)
+
+
 == 0.0.1 2008-11-26
 
 * 1 major enhancement:

data/README.rdoc

@@ -1,7 +1,11 @@
 = vixploder - "it may explode your vim"
 
 == DESCRIPTION:
-A simple 'dotfiles' management tool used to distribute common configuration files across multiple machines (initially consisting of a solid base for VIM, a few handy aliases for Rails development, and working with Git). The idea is not incredibly novel, but after realizing how poor the default VIM configuration is (at least on OS X), I wanted to be able to share mine with a few friends. Standard configuration files for other tools can easily be added to the tool, such as a core +.profile+, +.screenrc+ file, or Emacs config files...VIM is just the "test-case" for the distribution method at this point.
+A simple 'dotfiles' management tool used to distribute common configuration files across multiple machines.
+
+
+== DETAILS
+The idea is not incredibly novel, but after realizing how poor the default VIM configuration is (at least on OS X), I wanted to be able to share mine with a few friends. Standard configuration files for other tools can easily be added to the tool, such as a core +.profile+, +.screenrc+ file, or Emacs config files...VIM is just the "test-case" for the distribution method at this point.
 
 Vixploder is designed to give room for machine-/user-specific overrides. For example, the +.vimrc+ file sources a <tt>~/.local_vimrc</tt> file. These 'local dotfiles' are intentionally left out of version control and intended for settings that are either machine-specific or something a user may not want to be in a publicly-available repository. A couple examples of such content would be aliases for SSH-ing into a server with a particular username (ie: +site+ aliased to <tt>ssh my_username@my_website.com</tt>), or aliases to machine-specific paths for a project directory (both of these examples would be for your shell setup files, not vimrc, but the logic is the same...maybe you want a different colorscheme on a particular server in VIM).
 

data/Rakefile

@@ -5,7 +5,7 @@ require 'hanna/rdoctask'
 $hoe = Hoe.new('vixploder', Vixploder::VERSION) do |p|
   p.developer('Tom Kersten', 'tom@whitespur.com')
   p.changes              = p.paragraphs_of("History.txt", 0..1).join("\n\n")
-  p.post_install_message = File.read("PostInstall.txt").delete("\r")
+  p.post_install_message = p.paragraphs_of('PostInstall.txt', 0..10).join("\n\n")
   p.summary              = %q{Tool for simplifying the distribution of environment configuration files ('dotfiles') across multiple *nix-based nodes.}
   p.extra_dev_deps = [
     ['newgem', ">= #{::Newgem::VERSION}"]
@@ -13,7 +13,6 @@ $hoe = Hoe.new('vixploder', Vixploder::VERSION) do |p|
 
   p.clean_globs |= %w[**/.DS_Store tmp *.log]
   path = (p.rubyforge_name == p.name) ? p.rubyforge_name : "\#{p.rubyforge_name}/\#{p.name}"
-  p.remote_rdoc_dir = File.join(path.gsub(/^#{p.rubyforge_name}\/?/,''), 'rdoc')
   p.rsync_args = '-av --delete --ignore-errors'
 end
 

data/lib/dotfiles/vimrc

@@ -86,8 +86,10 @@ endif
 set foldmethod=syntax               "Syntax highlighting items specify folds
 
 "Not sure how I feel about these two yet
-set foldopen=all                    "Auto-opens folds on all possible 'autocmds'
-set foldclose=all                   "Auto-closes folds on all possible autocmds
+"Commenting out...probably not 'sane default' people would expect. Leaving 
+"for reference...
+"set foldopen=all                    "Auto-opens folds on all possible 'autocmds'
+"set foldclose=all                   "Auto-closes folds on all possible autocmds
 
 set foldtext=getline(v:foldstart)   "Set text displayed in "foldbar" when code is folded
 set fillchars=fold:\                "Fill foldline "empty space" with...empty spaces (instead of default "-" character)

data/lib/vixploder.rb

@@ -2,5 +2,5 @@ $:.unshift(File.dirname(__FILE__)) unless
   $:.include?(File.dirname(__FILE__)) || $:.include?(File.expand_path(File.dirname(__FILE__)))
 
 module Vixploder
-  VERSION = '0.1.3'
+  VERSION = '0.1.4'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: tomkersten-vixploder
 version: !ruby/object:Gem::Version 
-  version: 0.1.3
+  version: 0.1.4
 platform: ruby
 authors: 
 - Tom Kersten
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2009-01-12 00:00:00 -08:00
+date: 2009-01-13 00:00:00 -08:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -34,6 +34,8 @@ description: A simple 'dotfiles' management tool used to distribute common confi
 email: 
 - tom@whitespur.com
 executables: 
+- 256colors2.pl
+- colortest
 - vixplode
 extensions: []
 
@@ -155,9 +157,30 @@ files:
 - spec/vixplode_cli_spec.rb
 - spec/vixploder_spec.rb
 - tasks/rspec.rake
-has_rdoc: false
+has_rdoc: true
 homepage: 
-post_install_message: "    To use vixploder, execute:\n\n      vixplode\n\n    ...and try out VI. If you have issues with a blinking background\n    or errors on startup, confirm your system meets all the\n    requirements outlined in the README (http://bit.ly/m9Wk).\n\n    If you want to \"undo\" the changes, you can unlink the newly created\n    files in your home directory and restore them from ~/vixploder_backups:\n\n      mv ~/vixploder_backups/.* ~/\n\n    For more information on vixploder, see https://github.com/tomkersten/vixploder\n\n    NOTE: To create private Gists on http://gist.github.com, make sure you have set up\n    your username/token entries in your ~/.gitconfig file (refer to: http://bit.ly/OCgg)\n\n    Enjoy!\n"
+post_install_message: |+
+  
+  To use vixploder, execute:
+  
+    vixplode
+  
+  ...and try out VI. If you have issues with a blinking background
+  or errors on startup, confirm your system meets all the
+  requirements outlined in the README (http://bit.ly/m9Wk).
+  
+  If you want to "undo" the changes, you can unlink the newly created
+  files in your home directory and restore them from ~/vixploder_backups:
+  
+    mv ~/vixploder_backups/.* ~/
+  
+  For more information on vixploder, see https://github.com/tomkersten/vixploder
+  
+  NOTE: To create private Gists on http://gist.github.com, make sure you have set up
+  your username/token entries in your ~/.gitconfig file (refer to: http://bit.ly/OCgg)
+  
+  Enjoy!
+  
 rdoc_options: 
 - --main
 - README.rdoc