Shea Levy 98d1b64400 Initialize plugins after handling initial command line flags ... This is technically a breaking change, since attempting to set plugin files after the first non-flag argument will now throw an error. This is acceptable given the relative lack of stability in a plugin interface and the need to tie the knot somewhere once plugins can actually define new subcommands.		2021-02-24 08:22:17 -05:00
..
build-remote	Initialize plugins after handling initial command line flags	2021-02-24 08:22:17 -05:00
cpptoml	Revert the enum struct change	2020-06-18 22:11:26 +00:00
libcmd	Merge pull request #4541 from obsidiansystems/simpler-store-path-command	2021-02-19 16:18:53 +01:00
libexpr	Make missing auto-call arguments throw an eval error	2021-02-22 16:13:09 +01:00
libfetchers	Add traces to errors while updating flake lock file	2021-01-27 14:02:54 +01:00
libmain	Initialize plugins after handling initial command line flags	2021-02-24 08:22:17 -05:00
libstore	Initialize plugins after handling initial command line flags	2021-02-24 08:22:17 -05:00
libutil	Initialize plugins after handling initial command line flags	2021-02-24 08:22:17 -05:00
nix	Initialize plugins after handling initial command line flags	2021-02-24 08:22:17 -05:00
nix-build	Initialize plugins after handling initial command line flags	2021-02-24 08:22:17 -05:00
nix-channel	Initialize plugins after handling initial command line flags	2021-02-24 08:22:17 -05:00
nix-collect-garbage	Initialize plugins after handling initial command line flags	2021-02-24 08:22:17 -05:00
nix-copy-closure	Initialize plugins after handling initial command line flags	2021-02-24 08:22:17 -05:00
nix-env	Initialize plugins after handling initial command line flags	2021-02-24 08:22:17 -05:00
nix-instantiate	Initialize plugins after handling initial command line flags	2021-02-24 08:22:17 -05:00
nix-store	Initialize plugins after handling initial command line flags	2021-02-24 08:22:17 -05:00
resolve-system-dependencies	Fix macOS build	2021-01-21 12:46:22 +01:00