I hadn't planned on something so neat. I was just thinking I'd put them on the path with nonstandard executable names like `pvim` or `pcode`, and then people co

I hadn't planned on something so neat. I was just thinking I'd put them on the path with nonstandard executable names like `pvim` or `pcode`, and then people could use them in combination or not, individually enable-able as devenv modules. One of them could be aliased to `edit` or something like that if configured as the default editor, though. So the interface would look like editors.vim.enable = true; editors.vim.package = pkgs.neovim; editors.vim.plugins = []; editors.vscodium.enable = true; editors.defaultEditor = "vim"; and users would set or modify that in devenv.local.nix¹. And the editors module would handle constructing the customized editor packages from the specified base packages, lists of plugins/extensions, included config, etc., as well as wrapping them so that they are called by the names `pvim`, `pcode`, `edit`, etc., and pointing them to gitignored RC files that live in-repo which users can edit. -- https://devenv.sh/files-and-variables/ https://devenv.sh/files-and-variables/