I also sometimes have the opposite problem where it's not deleting enough. In other words, even when I remove all the relevant GC roots for a path it still won't get deleted even if `nix-store…
i think the one case where i can see wanting to change it is if, say, one of the repos in the registry were to ever change from master to main as the trunk development branch? or do we plan…
Yeah, I'd even suggest going further and making all of the nix command-line options automatically also configurable via nix.conf, although that's outside of the scope of this issue
nix does not propagate up to NixOS systems definitions
My best guess is that reason for the reimport of Nixpkgs is this:
4f7fd6dded/pkgs/build-support/testers/default.nix (L126)
Th…
I thought log-format = bar-with-logs was equivalent to setting --print-build-logs. See: 6c10cc0eda/src/libmain/loggers.cc (L33-L36)
Ah, okay, that makes sense. I agree that the online registry doesn't provide a lot of value: the entries there change slowly enough (almost never?) that changing them at lix upgrade time should…
Maybe make the --log-format option to many nix commands a global option one can set? Then I believe you could set log-format = bar-with-logs to get your desired behavior
:write to nix repl
Yeah, that's true, although the commands wouldn't have been lost; they would have just been written to the default history file path.
Another possible option that might give the best of both…
Can you explain a bit more then? I don't understand what the online flake registry is if it's different from the flake registry. More generally, I think perhaps I don't understand what is being…
I'm a little biased here because I actually use the indirect flake input feature all the time for quick and dirty local testing. I'll often do:
{ outputs = { nixpkgs, flake-utils,…I mean, you could make a similar argument against most things that rely on the --impure flag (like reading environment variables, local filesystem paths), but I don't think we're proposing to…
:write to nix repl
What I'm proposing is that if we added support for history files then we could include support for specifying the path to use for the history file in the REPL, like this:
nix-repl>…Or to put it another way: my understanding is that @jade is proposing to ban the use of the flake registry in flake.nix whereas I'm proposing to instead just require --impure to use the flake…
I think it wouldn't be basic daily usage, though? I'm not proposing that the CLI would require the --impure flag to use the flake registry. Only if you used the flake registry in flake.nix
Or perhaps permit the use of the flake registry (in flake.nix) if the user supplies the --impure flag?
:write to nix repl
I believe making the history file location configurable (e.g. via a command-line option or REPL command) would address that
No such file or directory in flakes is a terrible error message
Is there any reason we don't want to check the original directory to see if the file was there?
:write to nix repl
Would a .history file solve your issue? That seems to be like a more standard REPL feature that lots of line editing packages support out of the box. I think that would be simpler than rolling…