It is possible to make a commit with no files, e.g. with `--allow-empty`
or `--only` flags to `git-commit`. Previously, this hook would hang
indefinitely in those cases as `editorconfig-checker` with no file
arguments will read from stdin.
Many many people have complained about the misleading documentation.
Rather than continuing the path of "we need to fix this", we can reduce
the harmful effects of the inaccurate docs by removing them all
together.
Since much of the confusion in the "getting started" docs came from
`bud`-specific instructions, and `bud` is being removed, removing the
inaccurate docs also seems like it can be a kick towards replacing them.
Also:
- The NixOS manual is the canonical guide to installation. We don't need
to repeat its instructions.
- The numerous references to networking configuration don't have a place
within Digga -- I'm assuming these are `bud`-specific things which are
no longer relevant with `bud` gone.
This has been planned for some time.
It seems necessary to do so now because after updating inputs to track
NixOS 22.05 channels and releases, checks fail unexpectedly, with the
traces leading back to `bud`. Disabling its modules allows checks to
run successfully.
Rather than figuring out what's going wrong with `bud`, it seems more
appropriate to remove it as planned.
the `with pkgs` statement in `commands` muddies the origin of the
variables used within:
- editors are unable to provide helpful advice about undefined variables
because `with pkgs` acts as a blanket "anything is possible" signifier
- at a cursory glance, it may not be immediately clear that `system` is
coming from `pkgs.system`
- `lib` is coming from `pkgs.lib`, but we can use the `lib` module arg.
- some pkgs within `commands` are still referenced with
`pkgs.<package-name>` unnecessarily
while this could be considered a change in digga's api, flake-utils-plus
wouldn't allow duplicate hostnames either, because its `hosts` option
does not separate nixos or darwin hosts -- both live at `hosts.<hostname>`.
most of the `globalDefaults` module's definitions are not present in
nix-darwin, so they need to move into nixos-specific modules.
at this time, darwin does not yet have its own host-type-specific
defaults module, but there are probably some defs worth adding to such a
module.
