Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • dont-send-xp-features-to-the-daemon
  • build-with-clang
  • 2.3-maintenance
  • latest-release
  • ci-test-against-master-nix
  • test-daemon-everywhere
  • fix-manpages-install
  • be-gentle-on-missing-files-for-eval
  • search-to-pager
  • nix-init-command
  • nix-repl-experimental-features
  • nix-develop-remove-override-input-warning
  • macos-debugging
  • ca/remove-existing-invalid-store-path
  • eval-cache
  • ca/replicate-two-glibc
  • deduplicate-static-hashes-computation
  • boost-regex
  • cache-getflake
  • 2.3.15
  • 2.3.14
  • 2.3.13
  • 2.3.12
  • 2.3.11
  • 2.3.10
  • 2.3.9
  • 2.3.8
  • 2.3.7
  • 2.3.6
  • 2.3.5
  • 2.3.4
  • 2.3.3
  • 2.3.2
  • 2.3.1
  • 2.3
  • 2.2.2
  • 2.2.1
  • 2.2
  • 2.1.3
40 results
Blame Permalink
  • Shea Levy's avatar
    98d1b644
    Initialize plugins after handling initial command line flags · 98d1b644
    Shea Levy authored 
    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.
    Unverified
    98d1b644
    History
    Initialize plugins after handling initial command line flags
    Shea Levy authored 
    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.