Closed m15a closed 6 months ago
A few plugins such as rest.nvim (https://github.com/m15a/nixpkgs-vim-extra-plugins/issues/41) and mdeval.nvim (https://github.com/m15a/nixpkgs-vim-extra-plugins/issues/38) execute system commands. Is it maintainable to replace all such command paths with their full paths?
Example: https://github.com/m15a/nixpkgs-vim-extra-plugins/blob/965f751193747b8d58e64e3c856dfe410253d12e/overrides.nix#L239-L242
Ad-hoc patches like this would get broken once upstream changes codes. A better way could be to put such system commands to propagatedBuildInputs and let users wrap vim/nvim by using makeWrapper. Not sure. What's the best?
propagatedBuildInputs
makeWrapper
These kinds of fixes should be contributed by each plugin's users, including me. Lazy evaluation is worth it.
A few plugins such as rest.nvim (https://github.com/m15a/nixpkgs-vim-extra-plugins/issues/41) and mdeval.nvim (https://github.com/m15a/nixpkgs-vim-extra-plugins/issues/38) execute system commands. Is it maintainable to replace all such command paths with their full paths?
Example: https://github.com/m15a/nixpkgs-vim-extra-plugins/blob/965f751193747b8d58e64e3c856dfe410253d12e/overrides.nix#L239-L242
Ad-hoc patches like this would get broken once upstream changes codes. A better way could be to put such system commands to
propagatedBuildInputs
and let users wrap vim/nvim by usingmakeWrapper
. Not sure. What's the best?