nixpkgs/pkgs/misc/vim-plugins/default.nix

# TODO check that no license information gets lost
{ callPackage, config, lib, stdenv, vimUtils, vim, darwin, llvmPackages }:

let

  inherit (vimUtils.override {inherit vim;}) buildVimPluginFrom2Nix;

  plugins = callPackage ./generated.nix {
    inherit buildVimPluginFrom2Nix overrides;
  };

  # TL;DR
  # * Add your plugin to ./vim-plugin-names
  # * sort -udf ./vim-plugin-names > sorted && mv sorted vim-plugin-names
  # * run ./update.py
  #
  # If additional modifications to the build process are required,
  # add to ./overrides.nix.
  overrides = callPackage ./overrides.nix {
    inherit (darwin.apple_sdk.frameworks) Cocoa CoreFoundation CoreServices;
    inherit buildVimPluginFrom2Nix;
    inherit llvmPackages;
  };

  aliases = lib.optionalAttrs (config.allowAliases or true) (import ./aliases.nix lib plugins);

in

plugins // aliases
experimental/vim-vam-pathogen-vimrc-support This patch implements derving a .vimrc from vim-plugins.nix loading those plugins by either Pathogen or VAM (VAM seems to be slightly faster and is much more powerful). Example: environment.systemPackages = [ # default plain vim vim_configurable # vim which get's called vim-with-addon-nix (vim_configurable.customize { name = "vim-with-addon-nix"; vimrcConfig.vam.pluginDictionaries = [{name = "vim-addon-nix"; }]; }) ]; This way you can provide an "enhanced Vim" and a standard Vim. Details about what this commit changes: 1) provide a new toplevel name vimrc which * provides a way to build up a .vimrc using either pathogen or VAM (knowing about plugin dependencies by name) * can enhance vim to support. vim.customize { name = "name-user"; vam.pluginDictionaries and/or pathogen.pluginNames = .. } * introduce rtp names for each vim plugin pointing to the runtimepath path * suggest naming to be the same as vim-pi so that VAM's dependencies work * derive some packages as example from vim-pi using VAM's new autoload/nix.vim supporting simple dependencies * test case for vim-addon-nix for VAM/pathogen 2) enhance vim_configurable to support .customize 3) update many plugins by using VAM's implementation not rewriting those which * vim-pi doesn't know about the git source yet (TODO: make vim-pi be aware of those) * have special build code This commit partially conflicts with commits done by Bjørn Forsman starting by 37f961628b, eg the one using lower case attr and pkg names, because they don't match vim-pi (eg YouCompleteMe). Rather than resolving the conflict this just adds aliases so that both names can be used 2014-11-08 18:34:13 +00:00			`# TODO check that no license information gets lost`
vimPlugins: warn if alias is used inside overrides 2018-09-14 04:36:29 +00:00			`{ callPackage, config, lib, stdenv, vimUtils, vim, darwin, llvmPackages }:`
vim: supporting multiple sources: - vim-nox: client-server implementation without X - latest: latest mercurial sources (still very stable) - default: latest release vim-plugins: Introduce an area to put vim plugins which are worth adding to nix because they need more effort than just "unpacking". Document that 2013-05-27 16:29:35 +00:00
Refactoring vim plugins again: - sort automatcially generated vim derivations - move the plugins to be derived by VAM into its own file: vim-plugin-names - rename vimrc into vimUtils moving all common code into it so that it is possible to use it within ~/.nixpkgs/config.nix - Moving all important documentation into vimUtils - provide vimPlugins.pluginnames2Nix to provide a bin/vim-* command writing updated derivations into its buffer VAM's repository's nix.vim got some improvements @ VAM repository, eg hg fetchout out got fixed and shell failures are noticed now (Thanks to Arseniy Seroka) 2014-12-04 14:32:29 +00:00			`let`
experimental/vim-vam-pathogen-vimrc-support This patch implements derving a .vimrc from vim-plugins.nix loading those plugins by either Pathogen or VAM (VAM seems to be slightly faster and is much more powerful). Example: environment.systemPackages = [ # default plain vim vim_configurable # vim which get's called vim-with-addon-nix (vim_configurable.customize { name = "vim-with-addon-nix"; vimrcConfig.vam.pluginDictionaries = [{name = "vim-addon-nix"; }]; }) ]; This way you can provide an "enhanced Vim" and a standard Vim. Details about what this commit changes: 1) provide a new toplevel name vimrc which * provides a way to build up a .vimrc using either pathogen or VAM (knowing about plugin dependencies by name) * can enhance vim to support. vim.customize { name = "name-user"; vam.pluginDictionaries and/or pathogen.pluginNames = .. } * introduce rtp names for each vim plugin pointing to the runtimepath path * suggest naming to be the same as vim-pi so that VAM's dependencies work * derive some packages as example from vim-pi using VAM's new autoload/nix.vim supporting simple dependencies * test case for vim-addon-nix for VAM/pathogen 2) enhance vim_configurable to support .customize 3) update many plugins by using VAM's implementation not rewriting those which * vim-pi doesn't know about the git source yet (TODO: make vim-pi be aware of those) * have special build code This commit partially conflicts with commits done by Bjørn Forsman starting by 37f961628b, eg the one using lower case attr and pkg names, because they don't match vim-pi (eg YouCompleteMe). Rather than resolving the conflict this just adds aliases so that both names can be used 2014-11-08 18:34:13 +00:00
[bot] treewide: remove unused 'inherit' in let blocks 2018-07-20 19:36:12 +00:00			`inherit (vimUtils.override {inherit vim;}) buildVimPluginFrom2Nix;`
config.skipAliases: also disable vimPlugins, git, xfce and gnome3 aliases 2018-07-08 00:08:48 +00:00
vimPlugins: use fixed point 2018-12-27 10:12:48 +00:00			`plugins = callPackage ./generated.nix {`
			`inherit buildVimPluginFrom2Nix overrides;`
vimPlugins: added Rename (#19298) 2016-10-06 16:34:39 +00:00			`};`

vimPlugins: warn if alias is used inside overrides 2018-09-14 04:36:29 +00:00			`# TL;DR`
			`# * Add your plugin to ./vim-plugin-names`
			`# * sort -udf ./vim-plugin-names > sorted && mv sorted vim-plugin-names`
			`# * run ./update.py`
			`#`
			`# If additional modifications to the build process are required,`
			`# add to ./overrides.nix.`
			`overrides = callPackage ./overrides.nix {`
			`inherit (darwin.apple_sdk.frameworks) Cocoa CoreFoundation CoreServices;`
			`inherit buildVimPluginFrom2Nix;`
vim plugins: use v6.0 of the Clang library clighter8 plugin seems to be using python bindings for clang 6.0 clang_complete, another plugin using clang, works ok with this version 2018-09-22 15:52:35 +00:00			`inherit llvmPackages;`
vimPlugins: add changeColorScheme-vim 2015-07-09 02:09:13 +00:00			`};`

vimPlugins: use fixed point 2018-12-27 10:12:48 +00:00			`aliases = lib.optionalAttrs (config.allowAliases or true) (import ./aliases.nix lib plugins);`
config.skipAliases: also disable vimPlugins, git, xfce and gnome3 aliases 2018-07-08 00:08:48 +00:00
vimPlugins: warn if alias is used inside overrides 2018-09-14 04:36:29 +00:00			`in`
vim-plugins: rewrite updater A new python script has been added to replace the aged viml-based updater. The new updater has the following advantages: - use rss feeds to check for updates quicker - parallel downloads & better caching - uses proper override mechanism instead of text substitution - update generated files in-place instead of having to insert updated plugins manually Automatically reading `dependencies` from the plugins directory has been not re-implemented. This has been mostly been used by Mark Weber's plugins, which seem to no longer receive regular updates. This could be implemented in future as required. 2018-09-09 08:46:35 +00:00
vimPlugins: use fixed point 2018-12-27 10:12:48 +00:00			`plugins // aliases`