Repository navigation
v0.1.2
Nothing changes about how a document is drawn. This one is about getting termmd
onto a machine, and telling a shell what to do with it.
Added
--completions <SHELL>writes a completion script for bash, zsh, fish,
PowerShell or elvish, and--manwrites the man page as roff. Both are
generated from the same definition the flags are parsed with, so neither can
describe a termmd you do not have; both write to stdout without touching the
terminal, so redirecting one into a file cannot capture a capability probe.- Release archives carry the man page and the five completion scripts. They are
generated once per release rather than per target, because the cross-compiled
macOS build cannot run its own binary to produce them. brew install EdMUK/tap/termmdinstalls the release binary on macOS and
Linux, from a tap that does not
compile the crate.cargo binstall termmdfetches the release archive rather than compiling.
The manifest pins the naming the release workflow uses, which none of
binstall's defaults match.