vim-flavor 2.2.0 → 4.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 73cbe32362402bf8daa1f6951a8048e11dacf480
-  data.tar.gz: 14b6eee41cb928926aba70453825a08862471b67
+SHA256:
+  metadata.gz: 4b56f0299185327f581b7620d37b424150e44c4fbf9b644818f9a58430569116
+  data.tar.gz: a49bde472dcd149d79a41f4e260467cc8eb1da9865308536610667a00e50e598
 SHA512:
-  metadata.gz: 2f3b0ddc0fad3d8efcbddbced648050759c0b1fbb9ab8d0bf44ce7851da32b8df91a28611f829faca401f607710f2c45e66b4abc674f22c4e5b6f61f376b65fa
-  data.tar.gz: 95d6f8c557062bb1403affe71deb2bd187a0f29a1ffc7c329d40287ab2d2470360977072d2c341a3d42ed79047c8de13017a0113a85e3248b36398ddaadadf70
+  metadata.gz: a9babe8f14a01142a406f0e686c9a1b67ec7bae7418db50320af0ad55c348382b34e7b2a91dd9bfb5b7aa83486f403979a1cb45f3271a9b06365fe592d055605
+  data.tar.gz: 3a6f954a798748573d82de17b50b7fa0a6d11621f62231005a00699e3dd8fdb65d12d474a731153822b2b40e35d51e5398b39f1610555e21e3ea7cab4508c75a

data/.github/dependabot.yml

@@ -0,0 +1,12 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: "bundler" # See documentation for possible values
+    directory: "/" # Location of package manifests
+    schedule:
+      interval: "weekly"
+    versioning-strategy: increase

data/.github/workflows/ci.yml

@@ -0,0 +1,35 @@
+name: CI
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+  schedule:
+    - cron: 0 0 * * *
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+      with:
+        fetch-depth: 0 # t/blame.vim requires all commits.
+    - name: Set up Ruby
+      uses: ruby/setup-ruby@v1
+      with:
+        bundler-cache: true # runs 'bundle install' and caches installed gems automatically
+    - name: Set up Vim
+      uses: thinca/action-setup-vim@v1
+      with:
+        vim_version: ${{ github.event_name == 'schedule' && 'head' || 'v8.2.3446' }}
+        vim_type: vim
+        download: never # For some reason 'available' doesn't build from source as a fallback.
+    - name: Set up Git
+      run: |
+        git config --global user.email 'ci@example.com'
+        git config --global user.name 'CI'
+        git config --global init.defaultBranch 'master'
+        git submodule update --init
+    - name: Run tests
+      run: rake ci

data/.ruby-version

@@ -0,0 +1 @@
+3.0.2

data/README.md

@@ -1,76 +1,157 @@
 # vim-flavor, a tool to manage your favorite Vim plugins
 
-[![Build Status](https://travis-ci.org/kana/vim-flavor.png)](https://travis-ci.org/kana/vim-flavor)
-[![Code Climate](https://codeclimate.com/badge.png)](https://codeclimate.com/github/kana/vim-flavor)
+[![CI](https://github.com/kana/vim-flavor/actions/workflows/ci.yml/badge.svg)](https://github.com/kana/vim-flavor/actions/workflows/ci.yml)
+[![Maintainability](https://api.codeclimate.com/v1/badges/97414d95fb6d19c7fb72/maintainability)](https://codeclimate.com/github/kana/vim-flavor/maintainability)
 
 
 
 
-## Getting started
+# Getting started
 
-    cd $YOUR_REPOSITORY_FOR_DOTFILES
+## Create `Flavorfile`
 
-    cat >VimFlavor <<'END'
-      # * Declare using git://github.com/kana/vim-textobj-indent.git
-      # * vim-flavor fetches git://github.com/$USER/$REPO.git
-      #   if the argument is written in '$USER/$REPO' format.
-      # * kana/vim-textobj-indent requires kana/vim-textobj-user.
-      #   Such dependencies are automatically installed
-      #   if the flavored plugin declares its dependencies with VimFlavor file.
-      flavor 'kana/vim-textobj-indent'
+This file contains a set of declarations about what Vim plugins you want to
+install.  For example:
 
-      # * Declare using git://github.com/vim-scripts/fakeclip.git
-      # * vim-flavor fetches git://github.com/vim-scripts/$REPO.git
-      #   if the argument is written in '$REPO' format.
-      flavor 'fakeclip'
+```ruby
+# Install a Vim plugin from `https://github.com/kana/vim-textobj-indent`.
+#
+# Note that kana/vim-textobj-indent requires kana/vim-textobj-user.
+# Such dependencies are automatically installed if the former plugin
+# declares its dependencies with Flavorfile.
+flavor 'kana/vim-textobj-indent'
 
-      # * Declare using git://github.com/kana/vim-altr.git
-      # * vim-flavor fetches the URI
-      #   if the argument seems to be a URI.
-      flavor 'git://github.com/kana/vim-altr.git'
+# Install a Vim plugin from `https://github.com/vim-scripts/fakeclip`.
+flavor 'fakeclip'
 
-      # * Declare using kana/vim-smartchr 0.1.0 or later and older than 0.2.0.
-      flavor 'kana/vim-smartchr', '~> 0.1.0'
+# Install a Vim plugin from the specified URI.
+flavor 'git://github.com/kana/vim-altr.git'
 
-      # * Declare using kana/vim-smartword 0.1 or later and older than 1.0.
-      flavor 'kana/vim-smartword', '~> 0.1'
+# You can also specify which version of Vim plugin should be installed.
+# For example:
+flavor 'kana/vim-smartword', '~> 0.1'    # 0.1 or later, but older than 0.2
+flavor 'kana/vim-smartchr',  '~> 0.2.4'  # 0.2.4 or later, but older than 0.3.0
+flavor 'kana/vim-smarttill', '>= 0.3.6'  # 0.3.6 or later
 
-      # * Declare using kana/vim-smarttill 0.1.0 or later.
-      flavor 'kana/vim-smarttill', '>= 0.1.0'
-    END
+# vim-flavor, by design, requires Vim plugins to follow semantic versioning
+# and to create version tags (like `v1.2.3`) in their repositories.
+#
+# For repositories without versioning, branches can be specified.
+flavor 'chriskempson/base16-vim', branch: 'master'
+```
 
-    # Fetch the plugins declared in the VimFlavor,
-    # create VimFlavor.lock for a snapshot of all plugins and versions,
-    # then install the plugins and a bootstrap script into ~/.vim etc.
-    vim-flavor install
+## Install Vim plugins (for the first time)
 
-    # Add the following line into the first line of your vimrc:
-    #
-    #   runtime flavors/bootstrap.vim
-    vim vimrc
+Run the following command:
 
-    git add VimFlavor VimFlavor.lock vimrc
-    git commit -m 'Use vim-flavor to manage my favorite Vim plugins'
+```bash
+vim-flavor install
+```
 
-See also
-[the documentation on relish](https://www.relishapp.com/kana/vim-flavor) or
-`features/` directory for the details.
+This command does the following stuffs:
 
+1. Fetches Vim plugins declared in the `Flavorfile`.
+2. Creates `Flavorfile.lock` file.  It contains information about what
+   versions of plugins to be installed.
+3. Copies the fetched plugins into `~/.vim/pack/flavors/start`, then updates
+   help tags for each plugin.
 
+It's recommended to commit `Flavorfile` and `Flavorfile.lock` after
+installation.
 
+```bash
+git add Flavorfile Flavorfile.lock
+git commit -m 'Use vim-flavor to manage my favorite Vim plugins'
+```
 
-## License
+## Install Vim plugins (from another machine)
+
+Suppose that you work with several PCs and/or servers, and you want to use the
+same configuration, including Vim plugins, on all of them.
+
+Firstly, let's synchronize your configuration files:
+
+```bash
+cd ~/your/dotfiles/repository
+git pull
+```
+
+Now you have the same `Flavorfile` and `Flavorfile.lock` created by the
+previous step.
+
+Then run the following command:
+
+```bash
+vim-flavor install
+```
+
+This time `vim-flavor` installs the same versions of Vim plugins as recorded
+in `Flavorfile.lock`, even if newer versions are available.
+
+## Update Vim plugins
+
+To update Vim plugins, run the following command:
+
+```bash
+vim-flavor update
+```
+
+This is similar to `vim-flavor install`, but vim-flavor tries checking and
+installing newer versions of Vim plugins.
+
+This command usually updates `Flavorfile.lock`.  So that you have to commit it
+again.
+
+```bash
+git add Flavorfile.lock
+git commit -m 'Update Vim plugins'
+```
+
+
+
+
+# References
+
+See [`features/`](./features) directory for the details.
+The same [documents](https://www.relishapp.com/kana/vim-flavor) are available
+also on relish.
+
+
+
+
+# License
 
 vim-flavor is released under the terms of MIT license.
-See the LICENSE file for the details.
+See the [LICENSE](./LICENSE) file for the details.
+
+
+
+
+# Development
+
+## Set up
+
+1. Install [rbenv](https://github.com/rbenv/rbenv).
+2. Run the following commands in your clone of vim-flavor repository:
+
+   ```bash
+   git submodule update --init
+   rbenv install
+   bundle install
+   ```
+
+## Run tests
+
+```bash
+rake test
+```
 
 
 
 
-## Author
+# Author
 
-* [Kana Natsuno](http://whileimautomaton.net/)
-  (also known as [@kana1](http://twitter.com/kana1))
+* [kana](https://github.com/kana)
 
 
 

data/Rakefile

@@ -1,6 +1,12 @@
 #!/usr/bin/env rake
 require "bundler/gem_tasks"
 
+task :ci => [:dump, :test]
+
+task :dump do
+  sh 'vim --version'
+end
+
 task :test => [:spec, :cucumber]
 
 task :spec do
@@ -10,3 +16,8 @@ end
 task :cucumber do
   sh 'bundle exec cucumber --format=progress'
 end
+
+task :update_online_documents do
+  # Only authorized members can push to relish.
+  sh 'bundle exec relish push kana/vim-flavor'
+end

data/config/cucumber.yml

@@ -0,0 +1 @@
+default: --publish-quiet

data/features/.nav

@@ -11,7 +11,7 @@
 - flavorfile:
 - version_lock.feature
 - caching:
-- resolve_dependencies.feature
+- resolve_dependencies:
 - testing_vim_plugins:
   - typical_usage.feature
   - dependencies.feature
@@ -23,3 +23,4 @@
   - update.feature
   - changing_tracking_branches.feature
   - detect_incompatible_declarations.feature
+- backward_compatibilities:

data/features/backward_compatibilities/flavorfile.feature

@@ -0,0 +1,166 @@
+Feature: Flavorfile
+  In order to gradually update existing Vim plugins,
+  as a lazy Vim user,
+  I want to reuse Vim plugins which contain old name of flavorfiles without problems.
+
+  Scenario: User has old name of flavorfile is warned
+    Given a repository "foo" with versions "1.0.0 1.0.1 1.0.2"
+    And an old name flavorfile with:
+      """ruby
+      flavor '$foo_uri'
+      """
+    When I run `vim-flavor install`
+    Then it should pass with template:
+      """
+      Warning: Rename VimFlavor to Flavorfile.  VimFlavor wll be ignored in future version.
+      Checking versions...
+        Use $foo_uri ... 1.0.2
+      Deploying plugins...
+        $foo_uri 1.0.2 ... done
+      Completed.
+      """
+    And a lockfile is created with:
+      """
+      $foo_uri (1.0.2)
+      """
+    And a flavor "$foo_uri" version "1.0.2" is deployed to "$home/.vim"
+
+  Scenario: User has both new and old name of flavorfile is warned
+    Given a repository "foo" with versions "1.0.0 1.0.1 1.0.2"
+    And a repository "bar" with versions "2.0.0 2.0.1 2.0.2"
+    And a flavorfile with:
+      """ruby
+      flavor '$bar_uri'
+      """
+    And an old name flavorfile with:
+      """ruby
+      flavor '$foo_uri'
+      """
+    When I run `vim-flavor install`
+    Then it should pass with template:
+      """
+      Warning: Delete VimFlavor.  Flavorfile is being read instead.
+      Checking versions...
+        Use $bar_uri ... 2.0.2
+      Deploying plugins...
+        $bar_uri 2.0.2 ... done
+      Completed.
+      """
+    And a lockfile is created with:
+      """
+      $bar_uri (2.0.2)
+      """
+      And a flavor "$foo_uri" is not deployed to "$home/.vim"
+    And a flavor "$bar_uri" version "2.0.2" is deployed to "$home/.vim"
+
+  Scenario: Plugin contains old name of flavorfile is not warned
+    Given a repository "foo" with versions "1.0.0 1.0.1 1.0.2" and an old name flavorfile:
+      """ruby
+      # No dependencies
+      """
+    And a flavorfile with:
+      """ruby
+      flavor '$foo_uri'
+      """
+    When I run `vim-flavor install`
+    Then it should pass with template:
+      """
+      Checking versions...
+        Use $foo_uri ... 1.0.2
+      Deploying plugins...
+        $foo_uri 1.0.2 ... done
+      Completed.
+      """
+    And a lockfile is created with:
+      """
+      $foo_uri (1.0.2)
+      """
+    And a flavor "$foo_uri" version "1.0.2" is deployed to "$home/.vim"
+
+  Scenario: Testing a Vim plugin with old name flavorfile is warned
+    Given a repository "kana/vim-vspec" from offline cache
+    And an old name flavorfile with:
+      """ruby
+      # No dependencies
+      """
+    And a file named "plugin/foo.vim" with:
+      """vim
+      let g:foo = 3
+      """
+    And a file named "t/basics.vim" with:
+      """vim
+      " Tests are written with vim-vspec.
+      runtime! plugin/foo.vim
+      describe 'g:foo'
+        it 'is equal to 3'
+          Expect g:foo == 3
+        end
+      end
+      """
+    When I run `vim-flavor test`
+    Then it should pass with regexp:
+      """
+      -------- Preparing dependencies
+      Warning: Rename VimFlavor to Flavorfile.  VimFlavor wll be ignored in future version.
+      Checking versions...
+        Use kana/vim-vspec ... 1\.\d+(\.\d+)?
+      Deploying plugins...
+        kana/vim-vspec 1\.\d+(\.\d+)? ... done
+      Completed.
+      -------- Testing a Vim plugin
+      t/basics.vim .. ok
+      All tests successful.
+      Files=1, Tests=1,  \d+ wallclock secs .*
+      Result: PASS
+      """
+    And a lockfile is created and matches with:
+      """
+      kana/vim-vspec \(1\.\d+(\.\d+)?\)
+      """
+    And a dependency "kana/vim-vspec" is stored in ".vim-flavor/pack/flavors/start"
+
+  Scenario: Testing a Vim plugin with both new and old name flavorfile is warned
+    Given a repository "kana/vim-vspec" from offline cache
+    And a flavorfile with:
+      """ruby
+      # No dependencies
+      """
+    And an old name flavorfile with:
+      """ruby
+      # No dependencies
+      """
+    And a file named "plugin/foo.vim" with:
+      """vim
+      let g:foo = 3
+      """
+    And a file named "t/basics.vim" with:
+      """vim
+      " Tests are written with vim-vspec.
+      runtime! plugin/foo.vim
+      describe 'g:foo'
+        it 'is equal to 3'
+          Expect g:foo == 3
+        end
+      end
+      """
+    When I run `vim-flavor test`
+    Then it should pass with regexp:
+      """
+      -------- Preparing dependencies
+      Warning: Delete VimFlavor.  Flavorfile is being read instead.
+      Checking versions...
+        Use kana/vim-vspec ... 1\.\d+(\.\d+)?
+      Deploying plugins...
+        kana/vim-vspec 1\.\d+(\.\d+)? ... done
+      Completed.
+      -------- Testing a Vim plugin
+      t/basics.vim .. ok
+      All tests successful.
+      Files=1, Tests=1,  \d+ wallclock secs .*
+      Result: PASS
+      """
+    And a lockfile is created and matches with:
+      """
+      kana/vim-vspec \(1\.\d+(\.\d+)?\)
+      """
+    And a dependency "kana/vim-vspec" is stored in ".vim-flavor/pack/flavors/start"

data/features/backward_compatibilities/lockfile.feature

@@ -0,0 +1,22 @@
+Feature: Lockfile
+  In order to avoid unexpected result and confusion,
+  as a lazy Vim user,
+  I want to stop vim-flavor process if obsolete file still exists.
+
+  Scenario: User has old name of lockfile
+    Given a repository "foo" with versions "1.0.0 1.0.1 1.0.2"
+    And a flavorfile with:
+      """ruby
+      flavor '$foo_uri'
+      """
+    And an old name lockfile with:
+      """
+      $foo_uri (1.0.1)
+      """
+    When I run `vim-flavor install`
+    Then it should fail with template:
+      """
+      Error: VimFlavor.lock is no longer used.  Rename it to Flavorfile.lock.
+      """
+    And a lockfile is not created
+    And a flavor "$foo_uri" is not deployed to "$home/.vim"

data/features/branches/changing_tracking_branches.feature

@@ -24,7 +24,6 @@ Feature: Changing tracking branches
         $foo_uri $foo_rev_102 at master ... done
       Completed.
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.0.2" is deployed to "$home/.vim"
 
   Scenario: Use a branch instead of a version
@@ -49,7 +48,6 @@ Feature: Changing tracking branches
       """
       $foo_uri ($foo_rev_102 at master)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.0.2" is deployed to "$home/.vim"
 
   Scenario: Use a version instead of a branch
@@ -74,5 +72,4 @@ Feature: Changing tracking branches
       """
       $foo_uri (1.0.2)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.0.2" is deployed to "$home/.vim"

data/features/branches/detect_incompatible_declarations.feature

@@ -32,7 +32,6 @@ Feature: Detect incompatible declarations
         $L_uri branch: experimental is required by $B_uri
       Please resolve the conflict.
       """
-    And a bootstrap script is not created in "$home/.vim"
     And a flavor "$A_uri" is not deployed to "$home/.vim"
     And a flavor "$B_uri" is not deployed to "$home/.vim"
     And a flavor "$L_uri" is not deployed to "$home/.vim"
@@ -66,7 +65,6 @@ Feature: Detect incompatible declarations
         $L_uri ~> 0.2 is required by $B_uri
       Please resolve the conflict.
       """
-    And a bootstrap script is not created in "$home/.vim"
     And a flavor "$A_uri" is not deployed to "$home/.vim"
     And a flavor "$B_uri" is not deployed to "$home/.vim"
     And a flavor "$L_uri" is not deployed to "$home/.vim"

data/features/branches/install.feature

@@ -24,7 +24,6 @@ Feature: Install Vim plugins with specific branches
       """
       $foo_uri ($foo_rev_102 at master)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.0.2" is deployed to "$home/.vim"
 
   Scenario: Install a plugin according to a lockfile
@@ -47,5 +46,4 @@ Feature: Install Vim plugins with specific branches
         $foo_uri $foo_rev_102 at master ... skipped (already deployed)
       Completed.
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.0.2" is deployed to "$home/.vim"

data/features/branches/update.feature

@@ -26,5 +26,4 @@ Feature: Update Vim plugins with specific branches
         $foo_uri $foo_rev_103 at master ... done
       Completed.
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.0.3" is deployed to "$home/.vim"

data/features/caching/deployment.feature

@@ -9,6 +9,7 @@ Feature: Deployment
       """ruby
       flavor '$foo_uri', '~> 1.0'
       """
+
   Scenario: Deploy plugins which are not deployed yet
     Given a flavor "$foo_uri" is not deployed to "$home/.vim"
     When I run `vim-flavor install`

data/features/flavorfile/README.md

@@ -1,6 +1,6 @@
 Flavorfile is a DSL to declare which versions of Vim plugins to use.
 Whenever `vim-flavor` is invoked to manage Vim plugins,
-`vim-flavor` reads a file `VimFlavor` in the current working directory,
+`vim-flavor` reads a file `Flavorfile` in the current working directory,
 and evaluates it as a flavorfile.
 
 

data/features/flavorfile/comments.feature

@@ -19,5 +19,4 @@ Feature: Comments
     And a lockfile is created with:
       """
       """
-    And a bootstrap script is created in "$home/.vim"
     But a flavor "$foo_uri" is not deployed to "$home/.vim"

data/features/flavorfile/groups.feature

@@ -19,7 +19,6 @@ Feature: Groups
       """
       $foo_uri (1.2)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.2" is deployed to "$home/.vim"
     But a flavor "$bar_uri" is not deployed to "$home/.vim"
 
@@ -35,7 +34,6 @@ Feature: Groups
       """
       $foo_uri (1.2)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.2" is deployed to "$home/.vim"
     But a flavor "$bar_uri" is not deployed to "$home/.vim"
 
@@ -52,6 +50,5 @@ Feature: Groups
     And a lockfile is created with:
       """
       """
-    And a bootstrap script is created in "$home/.vim"
     But a flavor "$foo_uri" is not deployed to "$home/.vim"
     But a flavor "$bar_uri" is not deployed to "$home/.vim"

data/features/flavorfile/repository_name.feature

@@ -16,7 +16,6 @@ Feature: Repository name
       """
       vspec (0.0.4)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "vspec" version "0.0.4" is deployed to "$home/.vim"
 
   Scenario: Declare using a Vim plugin from GitHub
@@ -32,7 +31,6 @@ Feature: Repository name
       """
       kana/vim-vspec (0.0.4)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "kana/vim-vspec" version "0.0.4" is deployed to "$home/.vim"
 
   Scenario: Declare using a Vim plugin from an arbitrary URI
@@ -48,5 +46,4 @@ Feature: Repository name
       """
       $vspec_uri (0.0.4)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$vspec_uri" version "0.0.4" is deployed to "$home/.vim"

data/features/flavorfile/version_constraint.feature

@@ -3,10 +3,9 @@ Feature: Version constraint
   as a lazy Vim user,
   I want to declare desirable versions of Vim plugins.
 
-  Note that vim-flavor assumes that plugins follow [the versioning policies of
-  RubyGems](http://docs.rubygems.org/read/chapter/7#page26), to determine
-  compatibility of plugins.  See also [Philosophy](../philosophy) for the
-  details.
+  Note that vim-flavor assumes that plugins follow [Semantic Versioning
+  2.0.0](https://semver.org/spec/v2.0.0.html), to determine compatibility of
+  plugins.  See also [Philosophy](../philosophy) for the details.
 
   Background:
     Given a repository "foo" with versions "1.0 1.1 1.2 2.0"
@@ -22,7 +21,6 @@ Feature: Version constraint
       """
       $foo_uri (2.0)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "2.0" is deployed to "$home/.vim"
 
   Scenario: Declare using a Vim plugin not older than a specific version
@@ -36,7 +34,6 @@ Feature: Version constraint
       """
       $foo_uri (2.0)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "2.0" is deployed to "$home/.vim"
 
   Scenario: Declare using the latest and compatible version of a Vim plugin
@@ -50,5 +47,4 @@ Feature: Version constraint
       """
       $foo_uri (1.2)
       """
-    And a bootstrap script is created in "$home/.vim"
     And a flavor "$foo_uri" version "1.2" is deployed to "$home/.vim"