erikarvstedt

This seems to be fixed by #65. Wouldn't it make sense to always enable `zig-ansi-color-for-format-errors`? Why did you make it optional?

Which attributes are you interested in? System configuration? Container configuration? Current container state?

Is it that you want to use niv to pin the nixpkgs used for building a container? A simple way to achieve this would be to generate a `extra-container` wrapper...

Can you provide more details on what's your imagined, ideal workflow? Do you use direnv or nix-shell? How would the exact arguments to `extra-container` look like? Maybe something like this?...

I've just created nixpkgs PR [`extra-container: init at 0.5`](https://github.com/NixOS/nixpkgs/pull/102354).

Thanks for the suggestion, I'll fix that soon.

Great idea! Could you share a minimal config for a container that fails on startup?

``` extra-container add -s

1. `describe-buffer-bindings` already does that. For each active binding, unless it's defined globally, there's exactly one mode that provides it. This may be a major or a minor mode, but...

I failed to note that the proposed mechanism is not backwards compatible when `which-key-add-major-mode-key-based-replacements` was used to define replacements for bindings that are not actually provided by the major mode...