vimpack 0.0.1

data/.autotest

@@ -0,0 +1,13 @@
+begin
+  require "autotest/growl"
+rescue LoadError
+  puts 'Not going to growl'
+end
+Autotest.add_hook :initialize do |at|
+  at.add_exception %r%^\./\.autotest%
+  at.add_exception %r%^\./.git.%
+  at.add_exception %r%^\./tmp%
+  at.add_exception %r%^\./log%
+  at.add_exception %r%^\./rerun\.txt%
+  at.add_exception %r%^\./coverage%
+end

data/.gitignore

@@ -0,0 +1,6 @@
+.bundle
+*.swp
+tmp/*
+coverage/*
+Gemfile.lock
+cassette_library/*.yml

data/.rspec

@@ -0,0 +1,2 @@
+--color
+--format nested

data/.rvmrc

@@ -0,0 +1 @@
+rvm 1.9.2@vimpack_dev

data/Gemfile

@@ -0,0 +1,2 @@
+source "http://rubygems.org"
+gemspec

data/LICENSE

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) 2011 Bram Swenson
+
+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,47 @@
+# vimpack
+
+vim package manager
+
+### setup vimpack
+
+    # for now we install from the repo
+    $ git clone git@github.com:bramswenson/vimpack.git
+    $ cd vimpack
+    $ bundle install
+    $ rake build
+    $ gem install pkg/vimpack-0.0.1.gem
+    $ rake cucumber (if you want to run the tests)
+
+    $ vimpack init
+     * backing up existing vim environment
+     * initializing vimpack repo
+     * installing pathogen.vim
+     * initializing .vimrc
+    vimpack initialized!
+
+    $ vimpack search rails
+    rails.vim                       utility    
+    railscast                       colorscheme
+    Railscast There (GUI&256color)  colorscheme
+    railstab.vim                    utility    
+    FastGrep                        utility
+    apidock.vim                     utility
+    grails-vim                      utility
+    
+    $ vimpack info rails.vim
+    Name: rails.vim
+    Author: Tim Pope
+    Version: 4.3
+    Description: Ruby on Rails: easy file navigation, enhanced syntax highlighting, and more
+
+    $ vimpack install rails.vim
+     * installing rails.vim
+    rails.vim (4.3) installed!
+
+    $ vimpack list
+    rails.vim
+
+    $ vimpack uninstall rails.vim
+     * uninstalling rails.vim
+    rails.vim uninstalled!
+

data/Rakefile

@@ -0,0 +1,5 @@
+require 'bundler'
+Bundler::GemHelper.install_tasks
+
+Dir.glob(File.join(File.dirname(__FILE__), 'tasks/*.rake')).each {|f| load f }
+

data/autotest/discover.rb

@@ -0,0 +1,2 @@
+Autotest.add_discovery { "rspec2" }
+Autotest.add_discovery { "cucumber" }

data/bin/vimpack

@@ -0,0 +1,103 @@
+#!/usr/bin/env ruby
+
+require 'bundler/setup'
+begin
+  require 'vimpack'
+rescue LoadError => e
+  $LOAD_PATH.unshift(File.join(File.dirname(__FILE__), '..', 'lib'))
+  require 'vimpack'
+end
+
+USAGE = <<-EOU
+Manage bundles of vim scripts and vimrc
+
+Usage:
+
+  vimpack <subcommand>
+  vimpack <subcommand> --help      - Get more detailed help on subcommands
+  vimpack init [repo_url]          - Initialize vimpack repository
+  vimpack search <string>          - Search for scripts
+  vimpack install <script_name>    - Install scripts
+  vimpack uninstall <script_name>  - Uninstall scripts
+  vimpack list                     - List installed scripts
+  vimpack info <script_name>       - Get detailed info on a script
+  vimpack git publish -m <message> - Publish vimpack repo (shorthand for commit and push)
+  vimpack git <git command>        - Run any git command within the vimpack repo
+EOU
+
+SUB_COMMANDS = %w{ init search install uninstall list info git }
+global_options = Trollop::options do
+  version 'vimpack 0.0.1 (c) 2011 Bram Swenson'
+  banner USAGE
+  opt :environment, 'The environment to run vimpack within', :short => '-e', :default => 'production'
+  stop_on SUB_COMMANDS
+end
+
+cmd = ARGV.shift
+unless SUB_COMMANDS.include?(cmd)
+  Trollop::die USAGE
+end
+
+case cmd
+when 'init'
+  options = Trollop::options do
+    banner 'vimpack init [repo_url] - Initialize vimpack repository'
+    opt :home_directory, 'The home directory of the user', :short => '-d', :default => ENV['HOME']
+  end
+  Vimpack::Commands::Init.run(options, global_options)
+when 'search'
+  options = Trollop::options do
+    banner 'vimpack search <string> - Search for vim scripts'
+    opt :utility, 'Search for utility scripts', :short => '-u'
+    opt :color_scheme, 'Search for color scheme scripts', :short => '-c'
+    opt :syntax, 'Search for syntax scripts', :short => '-s'
+    opt :indent, 'Search for indent scripts', :short => '-i'
+    opt :game, 'Search for game scripts', :short => '-g'
+    opt :plugin, 'Search for plugin scripts', :short => '-p'
+    opt :patch, 'Search for patch scripts', :short => '-a'
+  end
+  Vimpack::Commands::Search.run(options, global_options)
+when 'install'
+  options = Trollop::options do
+    banner 'vimpack install <script_name> [script_name] - Install vim scripts'
+  end
+  Vimpack::Commands::Install.run(options, global_options)
+when 'uninstall'
+  options = Trollop::options do
+    banner 'vimpack uninstall <script_name> [script_name] - Uninstall vim scripts'
+  end
+  Vimpack::Commands::Uninstall.run(options, global_options)
+when 'list'
+  options = Trollop::options do
+    banner 'vimpack list - List installed vim scripts'
+  end
+  Vimpack::Commands::List.run(options, global_options)
+when 'info'
+  options = Trollop::options do
+    banner 'vimpack info <script_name> - Get detailed information on a vim script'
+  end
+  Vimpack::Commands::Info.run(options, global_options)
+when 'git'
+  the_banner = <<-EOB
+vimpack git publish -m <message> - Publish vimpack repo (shorthand for commit and push)
+vimpack git <git command>        - Run any git command within the vimpack repo
+EOB
+  git_command = ARGV.shift
+  parser = Trollop::Parser.new do
+    opt :message, 'publish message', :short => '-m',
+      :default => '[VIMPACK] vimpack publish' if git_command == 'publish'
+    banner the_banner
+  end
+  begin
+    options = parser.parse ARGV
+  rescue Trollop::CommandlineError => e
+    raise e if git_command == 'publish'
+    options = {}
+  end
+  ARGV.unshift git_command
+  Vimpack::Commands::Git.run(options, global_options)
+else
+  puts "command not found: #{cmd}"
+  Trollop::die USAGE
+end
+

data/cucumber.yml

@@ -0,0 +1,13 @@
+<%
+opts = '--color --require features'
+rerun = File.file?('rerun.txt') ? IO.read('rerun.txt') : ""
+rerun_opts = rerun.to_s.strip.empty? ? 
+  "#{opts} --format #{ENV['CUCUMBER_FORMAT'] || 'pretty'} features" : 
+  "#{opts} --format #{ENV['CUCUMBER_FORMAT'] || 'pretty'} #{rerun}"
+std_opts = "#{opts} --format #{ENV['CUCUMBER_FORMAT'] || 'pretty'} --strict --tags ~@wip"
+%>
+default: <%= std_opts %> features
+wip: <%= opts %> --tags @wip:3 --wip features
+rerun: <%= rerun_opts %> --format rerun --out rerun.txt --strict --tags ~@wip
+autotest: <%= std_opts %>
+autotest-all: <%= std_opts %>

data/features/commands/environments.feature

@@ -0,0 +1,26 @@
+Feature: Use different environments for vimpack
+
+  As a vimpack user
+  I want to use different environments
+  Mostly so I can test vimpack
+
+  Background: Setup test directories
+    Given a directory named "test_vimpack/.vim"
+      And an empty file named "test_vimpack/.vimrc"
+      And "test_vimpack" is my home directory
+
+  Scenario: Default environment should be production and should not alert
+    When I run `vimpack init`
+    Then the output should not contain " * using production environment!"
+      And the exit status should be 0
+
+  Scenario: When not in production environment we should be alerted
+    When I run `vimpack --environment development init`
+    Then the output should contain:
+    """
+     * using environment :development
+    """
+      And the output should not contain " * using production environment"
+      And the exit status should be 0
+
+

data/features/commands/git.feature

@@ -0,0 +1,77 @@
+Feature: Manage vimpack -e development git repo
+
+  As a vimpack user
+  I want manage my vimpack -e development git repo
+  So I can easily replicate my vimpack
+
+  Scenario: Publish vimpack to empty git repo
+    Given an initialized vimpack in "test_vimpack"
+      And an initialized git repo in "vimpack-repo"
+      And I run `vimpack -e development git remote add origin /tmp/aruba/vimpack-repo`
+    When I run `vimpack -e development git publish -m '[TEST] testing vimpack'`
+    Then the exit status should be 0
+      And the output should contain:
+        """
+         * publishing vimpack repo
+        vimpack repo published!
+        """
+      And the vimpack git remote "origin" should be "/tmp/aruba/vimpack-repo"
+
+  Scenario: Publish vimpack repo when out of sync
+    Given an initialized vimpack in "test_vimpack"
+      And "rails.vim" is already installed
+      And an existing git repo in "vimpack-repo"
+      And an initialized vimpack in "test_vimpack_remoted" from remote "vimpack-repo"
+      And "test_vimpack" is my home directory
+      And "cucumber.zip" is already installed
+      And I run `vimpack -e development git publish -m '[CUKE] added cucumber.zip'`
+      And "test_vimpack_remoted" is my home directory
+      And "haml.zip" is already installed
+    When I run `vimpack -e development git publish -m '[TEST] this is a fail!'`
+    Then the exit status should be 1
+      And the output should contain:
+        """
+        error: local repo out of sync with remote
+          use git to sync with something like this:
+           vimpack git fetch && vimpack git merge origin/master
+        """
+
+  Scenario: Initialize vimpack -e development git remote
+    Given an initialized vimpack in "test_vimpack"
+      And an initialized git repo in "vimpack-repo"
+    When I run `vimpack -e development git remote add origin /tmp/aruba/vimpack-repo`
+    Then the exit status should be 0
+      And the output should contain:
+        """
+         * running git remote add origin /tmp/aruba/vimpack-repo
+        command complete!
+        """
+      And the vimpack git remote "origin" should be "/tmp/aruba/vimpack-repo"
+
+  Scenario: Commit vimpack -e development git repo with commit message
+    Given an initialized vimpack in "test_vimpack"
+      And an initialized git repo in "vimpack-repo"
+      And I run `vimpack -e development git remote add origin /tmp/aruba/vimpack-repo`
+    When I run `vimpack -e development git add . `
+      And I run `vimpack -e development git commit -m '[TEST] test commit'`
+    Then the exit status should be 0
+      And the output should contain:
+        """
+         * running git commit -m [TEST] test commit
+        command complete!
+        """
+      And the vimpack git commit logs last message should be "[TEST] test commit"
+
+  Scenario: Publish vimpack -e development git repo
+    Given an initialized vimpack in "test_vimpack"
+      And an initialized git repo in "vimpack-repo"
+      And I run `vimpack -e development git remote add origin /tmp/aruba/vimpack-repo`
+      And "rails.vim" is already installed
+    When I run `vimpack -e development git publish`
+    Then the exit status should be 0
+      And the output should contain:
+        """
+         * publishing vimpack repo
+        vimpack repo published!
+        """
+      And the vimpack git status should be empty

data/features/commands/info.feature

@@ -0,0 +1,28 @@
+Feature: Get information about a script
+
+  As a vimpack user
+  I want to get information about a vim script
+  So I know more about what I am working with
+
+  Scenario: Get script detailed information
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development info rails.vim`
+    Then the output should contain:
+      """
+      Name: rails.vim
+      Author: Tim Pope
+      Version: 4.3 (2010-09-09T17:00:00-07:00)
+      Type: utility
+      Description: Ruby on Rails: easy file navigation, enhanced syntax highlighting, and more
+      """
+      And the exit status should be 0
+
+  Scenario: Try to get info for a script that does not exist
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development info this_does_not_exists_i_swear`
+    Then the output should contain:
+      """
+      Script not found!
+      """
+      And the exit status should be 1
+

data/features/commands/init.feature

@@ -0,0 +1,47 @@
+Feature: Initialize vimpack
+
+  As a vimpack user
+  I want to initialize vimpack
+  So I can have a sane way to manage vim scripts
+
+  Scenario: Initialize vimpack in an existing vim environment
+    Given a directory named "test_vimpack/.vim"
+      And an empty file named "test_vimpack/.vimrc"
+      And "test_vimpack" is my home directory
+    When I run `vimpack -e development init`
+    Then a directory named "test_vimpack/.vim.before_vimpack" should exist
+      And a file named "test_vimpack/.vimrc.before_vimpack" should exist
+      And the output should contain " * initializing vimpack repo"
+      And a directory named "test_vimpack/.vimpack" should exist and be a git repo
+      And a directory named "test_vimpack/.vimpack/vim" should exist
+      And a directory named "test_vimpack/.vimpack/vim/autoload" should exist
+      And a directory named "test_vimpack/.vimpack/vim/bundle" should exist
+      And a directory named "test_vimpack/.vimpack/scripts" should exist
+      And a symlink named "test_vimpack/.vim" should exist and link to "test_vimpack/.vimpack/vim"
+      And a directory named "test_vimpack/.vimpack/scripts/utility/pathogen.vim" should exist and be a git submodule of "test_vimpack/.vimpack"
+      And a symlink named "test_vimpack/.vimpack/vim/autoload/pathogen.vim" should exist and link to "test_vimpack/.vimpack/scripts/utility/pathogen.vim/plugin/pathogen.vim"
+      And a symlink named "test_vimpack/.vimrc" should exist and link to "test_vimpack/.vimpack/vimrc"
+      And the output should contain "vimpack initialized!"
+      And the exit status should be 0
+
+  Scenario: Initialize vimpack from git repo
+    Given a directory named "test_vimpack/.vim"
+      And an empty file named "test_vimpack/.vimrc"
+      And "test_vimpack" is my home directory
+    When I run `vimpack -e development init git@github.com:bramswenson/vimpack-repo-test.git`
+    Then a directory named "test_vimpack/.vim.before_vimpack" should exist
+      And a file named "test_vimpack/.vimrc.before_vimpack" should exist
+      And the output should contain " * initializing vimpack repo from git@github.com:bramswenson/vimpack-repo-test.git"
+      And a directory named "test_vimpack/.vimpack" should exist and be a git repo
+      And a directory named "test_vimpack/.vimpack/vim" should exist
+      And a directory named "test_vimpack/.vimpack/vim/autoload" should exist
+      And a directory named "test_vimpack/.vimpack/vim/bundle" should exist
+      And a directory named "test_vimpack/.vimpack/scripts" should exist
+      And a symlink named "test_vimpack/.vim" should exist and link to "test_vimpack/.vimpack/vim"
+      And a directory named "test_vimpack/.vimpack/scripts/utility/pathogen.vim" should exist and be a git submodule of "test_vimpack/.vimpack"
+      And a symlink named "test_vimpack/.vimpack/vim/autoload/pathogen.vim" should exist and link to "test_vimpack/.vimpack/scripts/utility/pathogen.vim/plugin/pathogen.vim"
+      And a symlink named "test_vimpack/.vimrc" should exist and link to "test_vimpack/.vimpack/vimrc"
+      And the output should contain "vimpack initialized!"
+      And the vimpack git remote "origin" should be "git@github.com:bramswenson/vimpack-repo-test.git"
+      And the exit status should be 0
+

data/features/commands/install.feature

@@ -0,0 +1,50 @@
+Feature: Install a vim script
+
+  As a vimpack user
+  I want to install a vim script
+  So I can use it in vim
+
+  Scenario: Install a script
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development install rails.vim`
+    Then the output should contain:
+      """
+       * installing rails.vim
+      rails.vim (4.3) installed!
+      """
+      And a directory named "test_vimpack/.vimpack/scripts/utility/rails.vim" should exist and be a git submodule of "test_vimpack/.vimpack"
+      And a symlink named "test_vimpack/.vimpack/vim/bundle/rails.vim" should exist and link to "test_vimpack/.vimpack/scripts/utility/rails.vim"
+      And the exit status should be 0
+
+  Scenario: Install multiple scripts
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development install rails.vim cucumber.zip`
+    Then the output should contain:
+      """
+       * installing rails.vim
+      rails.vim (4.3) installed!
+       * installing cucumber.zip
+      cucumber.zip (1.0) installed!
+      """
+      And a directory named "test_vimpack/.vimpack/scripts/utility/rails.vim" should exist and be a git submodule of "test_vimpack/.vimpack"
+      And a symlink named "test_vimpack/.vimpack/vim/bundle/rails.vim" should exist and link to "test_vimpack/.vimpack/scripts/utility/rails.vim"
+      And the exit status should be 0
+
+  Scenario: Attempt to install a script that is not found
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development install railz`
+    Then the output should contain:
+      """
+      Script not found!
+      """
+      And the exit status should be 1
+
+  Scenario: Attempt to install a script that is not found but a fuzzy match is found
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development install cucumber`
+    Then the output should contain:
+      """
+      Script not found! Did you mean cucumber.zip?
+      """
+      And the exit status should be 1
+

data/features/commands/list.feature

@@ -0,0 +1,18 @@
+Feature: List installed vim script
+
+  As a vimpack user
+  I want to list installed vim script
+  So I know what I am working with
+
+  Scenario: List installed vim scripts
+    Given an initialized vimpack in "test_vimpack"
+     And "rails.vim" is already installed
+     And "railscasts" is already installed
+    When I run `vimpack -e development list`
+    Then the stdout should contain:
+      """
+      rails.vim
+      railscasts
+      """
+      And the exit status should be 0
+

data/features/commands/search.feature

@@ -0,0 +1,137 @@
+Feature: Search for a vim script
+
+  As a vimpack user
+  I want to search for a vim script
+  So I can find a script to install
+
+  Scenario: Search for a script
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development search rails`
+    Then the output should contain:
+      """
+      rails.vim                        utility
+      railscasts                       color scheme
+      Railscasts-Theme-GUIand256color  color scheme
+      railstab.vim                     utility
+      FastGrep                         utility
+      apidock.vim                      utility
+      grails-vim                       utility
+      paper                            color scheme
+      """
+      And the exit status should be 0
+
+  Scenario: Search for a script within multiple script_types
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development search --utility --color-scheme rails`
+    Then the output should contain:
+      """
+      rails.vim                        utility
+      railscasts                       color scheme
+      Railscasts-Theme-GUIand256color  color scheme
+      railstab.vim                     utility
+      FastGrep                         utility
+      apidock.vim                      utility
+      grails-vim                       utility
+      paper                            color scheme
+      """
+      And the exit status should be 0
+
+  Scenario: Search for a utility script
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development search --utility rails`
+    Then the output should contain:
+      """
+      rails.vim     utility
+      railstab.vim  utility
+      FastGrep      utility
+      apidock.vim   utility
+      grails-vim    utility
+      """
+      And the exit status should be 0
+
+  Scenario: Search for all utility scripts
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development search --utility`
+    Then the output should contain:
+      """
+      test.vim              utility
+      test.zip              utility
+      ToggleCommentify.vim  utility
+      keepcase.vim          utility
+      vimbuddy.vim          utility
+      buffoptions.vim       utility
+      fortune.vim           utility
+      drawing.vim           utility
+      ctags.vim             utility
+      closetag.vim          utility
+      """
+      And the exit status should be 0
+
+  Scenario: Search for a color scheme script
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development search --color-scheme rails`
+    Then the output should contain:
+      """
+      railscasts                       color scheme
+      Railscasts-Theme-GUIand256color  color scheme
+      paper                            color scheme
+      """
+      And the exit status should be 0
+
+  Scenario: Search for a syntax script
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development search --syntax haml`
+    Then the output should contain:
+      """
+      haml.zip  syntax
+      Haml      syntax
+      """
+      And the exit status should be 0
+
+  Scenario: Search for an indent script
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development search --indent ruby`
+    Then the output should contain:
+      """
+      indentruby.vim     indent
+      ruby.vim--IGREQUE  indent
+      """
+      And the exit status should be 0
+
+  Scenario: Search for a game script
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development search --game sudoku`
+    Then the output should contain:
+      """
+      sudoku         game
+      Sudoku-Solver  game
+      """
+      And the exit status should be 0
+
+  Scenario: Search for a plugin script
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development search --plugin apt`
+    Then the output should contain:
+      """
+      apt-complete.vim  plugin
+      """
+      And the exit status should be 0
+
+  Scenario: Search for a patch script
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development search --patch start`
+    Then the output should contain:
+      """
+      startup_profile  patch
+      """
+      And the exit status should be 0
+
+  Scenario: Search for an unknown script
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development search this_does_not_exist_anywhere_right`
+    Then the output should contain:
+      """
+      No scripts found!
+      """
+      And the exit status should be 0
+

data/features/commands/uninstall.feature

@@ -0,0 +1,46 @@
+Feature: Uninstall a vim script
+
+  As a vimpack user
+  I want to uninstall a vim script
+  So its not taking up space
+
+  Scenario: Uninstall a script
+    Given an initialized vimpack in "test_vimpack"
+     And "rails.vim" is already installed
+    When I run `vimpack -e development uninstall rails.vim`
+    Then the output should contain:
+      """
+       * uninstalling rails.vim
+      rails.vim uninstalled!
+      """
+      And a symlink named "test_vimpack/.vimpack/vim/bundle/rails.vim" should not exist
+      And a directory named "test_vimpack/.vimpack/scripts/utility/rails.vim" should not exist
+      And the exit status should be 0
+
+  Scenario: Uninstall multiple scripts
+    Given an initialized vimpack in "test_vimpack"
+     And "rails.vim" is already installed
+     And "cucumber.zip" is already installed
+    When I run `vimpack -e development uninstall rails.vim cucumber.zip`
+    Then the output should contain:
+      """
+       * uninstalling rails.vim
+      rails.vim uninstalled!
+       * uninstalling cucumber.zip
+      cucumber.zip uninstalled!
+      """
+      And a symlink named "test_vimpack/.vimpack/vim/bundle/rails.vim" should not exist
+      And a directory named "test_vimpack/.vimpack/scripts/utility/rails.vim" should not exist
+      And a symlink named "test_vimpack/.vimpack/vim/bundle/cucumber.zip" should not exist
+      And a directory named "test_vimpack/.vimpack/scripts/utility/cucumber.zip" should not exist
+      And the exit status should be 0
+
+  Scenario: Try Uninstall a script that is not installed
+    Given an initialized vimpack in "test_vimpack"
+    When I run `vimpack -e development uninstall rails.vim`
+    Then the output should contain:
+      """
+      Script not found!
+      """
+      And the exit status should be 1
+