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
..
cpptools	treewide: use runtimeShell instead of stdenv.shell whenever possible	2019-02-26 14:10:49 +00:00
python	vscode-extensions.ms-python.python: 2018.11.0 -> 2018.12.1	2018-12-18 12:27:44 -05:00
wakatime	vscode-extensions.WakaTime.vscode-wakatime: 1.2.5 -> 1.2.7	2019-02-25 20:37:51 -05:00
default.nix	vscode-extensions.WakaTime.vscode-wakatime: init at 1.2.3	2018-11-20 17:35:23 -05:00
update_installed_exts.sh	vscode-extensions: script to generate Nix for "latest" version of all installed vscode extensions	2018-08-07 10:14:57 +10:00
vscode-utils.nix	vscode-extensions.WakaTime.vscode-wakatime: init at 1.2.3	2018-11-20 17:35:23 -05:00