Recent commits to derivepassphrase.git (672943aac976f3272c72a1d5e5608b1e3c4fd183)

Merge topic branch 'usage-fixes' into master

2025-01-07T11:13:37+01:00

* t/usage-fixes:
  Consolidate and slightly simplify some warning message emittances
  Add tests for help and version options, and color forcing
  Fix check of empty service name for `derivepassphrase vault`
</pre>

Consolidate and slightly simplify some warning message emittances

2025-01-07T11:09:38+01:00

</pre>

Add tests for help and version options, and color forcing

2025-01-01T14:08:48+01:00

These sections no longer need be excluded from coverage.
</pre>

Fix check of empty service name for `derivepassphrase vault`

2025-01-01T02:02:43+01:00

We asserted in c1bf00eadd1bf733ac25a25eafbe110d61936c54 that an empty
service name is both diagnosed, then treated as if it were missing later
on.  This wasn't actually strictly true: the checks for a missing or
superfluous service name tested for truthy service names instead of
non-missing service names, and the key selection and passphrase entry
dialogs happen before the check for a non-empty service name.  Fix these
two issues by checking for non-missing service names in the former case,
and moving the non-empty service name check further to the front in the
latter case.
</pre>

Merge topic branch 'no-color-force-color' into master

2025-01-01T00:57:42+01:00

* t/no-color-force-color:
  Add a changelog entry for the color suppressing/forcing support
  Support suppressing or forcing color output
</pre>

Add a changelog entry for the color suppressing/forcing support

2025-01-01T00:56:43+01:00

</pre>

Support suppressing or forcing color output

2025-01-01T00:47:57+01:00

We implement this with an eager, hidden "pseudo" option that checks for
the `NO_COLOR` and `FORCE_COLOR` options and sets the context's color
setting appropriately.

To actually make use of this color setting, all output must query the
context's color setting, as must all log output.  For the log output
specifically, we arrange to pass the `click` context in the extra dict
of each logging call, so that the handler has access to the color
setting too.
</pre>

Merge topic branch 'shell-completion' into master

2025-01-01T00:30:14+01:00

* t/shell-completion:
  Add changelog entry for the new explicit shell completion support
  Add shell completion support to derivepassphrase
</pre>

Add changelog entry for the new explicit shell completion support

2025-01-01T00:28:20+01:00

</pre>

Add shell completion support to derivepassphrase

2025-01-01T00:21:55+01:00

`click` already includes shell completion out of the box, so what
remained to be done was to tell `click` what kind of values the
arguments expect:

  * The `path` argument for `derivepassphrase export vault` will be
    completed with a filename or the string `VAULT_PATH`.  Because this
    is not (as a whole) a supported standard category of completion
    items, we must generate the completion items ourselves in this case,
    including the partial filtering of results.

  * The `path` argument to the `--import` and `--export` options of
    `derivepassphrase vault` will be completed with a filename.  `click`
    handles this for us.

  * The `service` argument to `devirepassphrase vault` will be completed
    with a service name, which we must manually extract and filter.

The shell completion has so far only been tested interactively; in
particular, it is currently excluded from coverage testing.
</pre>