Pfalzgraf Martin

I'll be honest, requiring extra options is less than ideal. Instead have `nix init` check for a `./shell.nix` file and a `./nix/default.nix` file. If there is only a `./shell.nix` then...

I agree that having a simple enough example to build off of is a good idea. I would extend this idea by also generating a `shell.nix` that imports everything from...

Why not have both? Keep the existing behavior of `sources.nix` and just tack on an extra attribute called `buildInputs` to make creating a `shell.nix` easy (or have niv generate the...

Sadly `nix-shell --command "ghcide --lsp"` won't work if its evoked by the editor since (I think) the editor is trying to talk to the `nix-shell` process instead of `ghcide`. It...

@mpickering I assume you are running `nix-shell --command "ghcide --lsp"` in a separate shell, not using your editor, and then setting up your editor to communicate with that `ghcide` instance....

I ran into this while doing a multi-user Nix installation on AlmaLinux. Xbreak's solution mentioned in a nixpkgs [issue](https://github.com/NixOS/nixpkgs/issues/70939) worked for me: `systemctl edit nix-daemon.service`, paste in: ``` [Service] Environment="NIX_SSL_CERT_FILE=/etc/ssl/certs/ca-bundle.crt"...

Another reason for size to be constrained: a negative size results in confusing results for those who have not figured out it is only valid for 0-99. Documentation could help...

Yes, the cleanup should only run if there is not a failure. My thoughts are: If there is a `Command` that fails in some sequence/parallel execution of commands then its...

You are right that a cleanup function would not run if one command failed in the sequence of commands, just like I'm after. The problem is deriving the cleanup actions...

Adding a cleanup `Command` at the end is not the right solution. If we use a `Command` the type would allow you to do things you wouldn't want in a...