2 ms·

I was also motivated in this direction by some friends I want to teach to code. There's so much for a newbie to overcome that has nothing to do with code. Wha

I was also motivated in this direction by some friends I want to teach to code. There's so much for a newbie to overcome that has nothing to do with code. What I'm struggling with right now is: How do you make supplying your own vim, say, versus the one that's default for this project... How do you make that feel like supplying a nondefault "Editor" type argument to a function? I'm aware that flake inputs support that sort of trickery via input overrides from the CLI, but there's nothing about that (besides perhaps the name of the input) which ensures that you only put editors in that slot. And then correspondingly, editors are a bit too varied to be interchangable like that. If a project defaults to VSCodium and I want to inject helix... that's like gonna take some hackery which prevents it from feeling like dependency-injected magic.

pxc 2y ago
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/

pxc 2y ago

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/