Jörg Thalheim dadc7eb329 treewide: use runtimeShell instead of stdenv.shell whenever possible ... Whenever we create scripts that are installed to $out, we must use runtimeShell in order to get the shell that can be executed on the machine we create the package for. This is relevant for cross-compiling. The only use case for stdenv.shell are scripts that are executed as part of the build system. Usages in checkPhase are borderline however to decrease the likelyhood of people copying the wrong examples, I decided to use runtimeShell as well.		2019-02-26 14:10:49 +00:00
..
patches/vim-grammarous	vimPlugins.vim-grammarous: set languagetool path	2017-11-21 17:05:55 +00:00
vim2nix	vim: remove legacy additional-nix-code	2018-09-23 14:56:27 +01:00
aliases.nix	vimPlugins: warn if alias is used inside overrides	2018-09-14 08:59:01 -07:00
build-vim-plugin.nix	vimUtils.buildVimPlugin: write vim errors to stderr	2019-01-18 21:18:35 +01:00
default.nix	vimPlugins: use fixed point	2018-12-27 11:55:53 +01:00
generated.nix	vimPlugins: Update	2019-02-16 21:01:32 +01:00
overrides.nix	LanguageClient-neovim: 2018-09-07 -> 0.1.140	2019-02-15 23:17:36 +01:00
update.py	vimPlugins: Fix update.py, update (#53081)	2018-12-30 18:13:00 +01:00
vim-plugin-names	Merge pull request #54590 from symphorien/sved2	2019-01-26 09:20:34 +00:00
vim-utils.nix	treewide: use runtimeShell instead of stdenv.shell whenever possible	2019-02-26 14:10:49 +00:00