Recent commits to derivepassphrase.git (4b0cfe2631b1699a456ec3465405db4f7ca65376)

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>

Merge topic branch 'i18n-l10n-infrastructure' into master

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

* t/i18n-l10n-infrastructure:
  Add a changelog entry for the new i18n/l10n infrastructure
  Fix coverage
  Reimplement `--help` and `--version` options in a translatable way
  Replace strings in `derivepassphrase export vault` with translatable ones
  Force logging calls in error callback to be uninterpolated
  Provide a function to reload translations for derivepassphrase
  Add a writer function for derivepassphrase's .po template
  Fix some translation typos and inconsistent translation comments
  Update the CLI to use the translatable strings
  Add more translatable strings and serialization machinery
  Extract translatable log messages into separate module
  Add an actual derivepassphrase-vault(1) manpage, plus better manpage contents
  Make the mutually exclusive options helper function print the correct parameter name
  Add small fixes to changelog, docstrings and variable names
</pre>

Add a changelog entry for the new i18n/l10n infrastructure

2025-01-01T00:17:17+01:00

</pre>

Fix coverage

2024-12-31T23:58:59+01:00

Exclude further machinery from coverage that isn't meant to be tested.
</pre>

Reimplement `--help` and `--version` options in a translatable way

2024-12-31T22:30:36+01:00

Reimplement the machinery for displaying help texts and version
information, supporting translatable strings.  Besides the one-line help
texts for the `--help` and `--version` options, the version information
text is a translatable string itself, in case the name and version
number should be rearranged, or prefixed or suffixed, or whatever.
</pre>