vim_configurable and neovim have both supported a mechanism to build
them with a custom vimrc that supports plugins from Nix. This updates
MacVim to support the same sort of configuration using an expression
like
macvim.configure {
customRC = ''
# custom configuration goes here
'';
packages.myVimPackage = with pkgs.vimPlugins; {
start = [ youcompleteme fugitive ];
opt = [ phpCompletion elm-vim ];
}
}
Once configured, .override will allow for editing the configuration.
Like vim_configurable and neovim, configuring macvim does not require
rebuilding it. Also like them, configuring macvim turns off the user
vimrc file.
* programs.neovim: init
Allows to build a proper runtime folder with after/ ftplugin/ parser/ subfolders etc.
(neo)vim expects a few different folders, for instance to load
treesitter parsers.
This PR reuses the builder from the etc module, notwithstanding the
different modes/uid/gid.
This allows to get rid of some autocmd in customRC (via proper use of
the folder hierarchy) which is a win in my opinion.
pyvips: init at 2.1.12
pyvips: init at 2.1.12
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
Update pkgs/top-level/python-packages.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
pyvips: init at 2.1.12
Update pkgs/development/python-modules/pyvips/default.nix
Co-authored-by: Jon <jonringer@users.noreply.github.com>
Add version to binaries produced via patchGoModVendor to allow run-time provider
version validation by terraform.
This was initially introduced in 4e63119c540 (terraform: add the version component to terraform provider paths (#34497), 2018-02-06)
but broken in 3e5149a79ad (terraform-providers: fix the google and google-beta providers, 2020-03-24)
for terraform-providers.google and terraform-providers.google-beta, and in 20f55a9fc07 (terraform-providers.ibm: move to update-all script, 2020-04-26)
for terraform-providers.ibm.
