anchor.diff:        sha256 = "1348gzp0zhc2wifvs5vmf92m9y8ik8ldnvy7bawsxahy8hmhiksk";
       };
   
  -    installPhase = ''
  -      mkdir -p "$out/vim-plugins"
  -      cp -R plugin "$out/vim-plugins"
  -    '';
  +    path = "xdebug";
   
       postInstall = false;
     };
   }
  -
  
positive.code:   set rtp+=~/.nix-profile/vim-plugins/YouCompleteMe
    " or for p in ["YouCompleteMe"] | exec 'set rtp+=~/.nix-profile/vim-plugins/'.p | endfor
  
  Its what
  pathogen, vundle, vim-addon-manager (VAM) use.
  
  VAM's benefits:
  - works around after/* directories if they are used in non ~/.vim locations
  - allows activating plugins at runtime, eg when you need them. (works around
    some au command hooks, eg required for TheNerdTree plugin)
  - VAM checkous out all sources (vim.sf.net, git, mercurial, ...)
  - runs :helptags on update/installation only. Obviously it cannot do that on
    store paths.
  
  VAM is made up of
  - the code loading plugins
  
negative.code:     };
    };
  
    syntastic = simpleDerivation {
      name = "vim-syntastic-3.0.0";
      src = fetchurl {
        url = "https://github.com/scrooloose/syntastic/archive/3.0.0.tar.gz";
        sha256 = "0nf69wpa8qa7xcfvywy2khmazs4dn1i2nal9qwjh2bzrbwbbkdyl";
      };
      path = "syntastic";
    };
  
    coffeeScript = simpleDerivation {
      name = "vim-coffee-script-v002";
      src = fetchurl {
        url = "https://github.com/vim-scripts/vim-coffee-script/archive/v002.tar.gz";
        sha256 = "1xln6i6jbbihcyp5bsdylr2146y41hmp2xf7wi001g2ymj1zdsc0";
      };
      path = "vim-coffee-script";
    };
  
    command_T = simpleDerivation {
  
      name = "vim-command-t-1.4";
  
      src = fetchurl {
        url    = "https://github.com/wincent/Command-T/archive/1.4.tar.gz";
        sha256 = "1ka9hwx9n0vj1dd5qsd2l1wq0kriwl76jmmdjzh7zaf0p547v98s";
      };
  
      path = "Command-T";
  
      buildInputs = [ perl ruby ];
  
  