This is forked from issue #17, where @DiederikvandenB reported that chasquid-util aliases-resolve does not take hooks into account, and that is confusing and misleading.
At minimum, the documentation should mention this fact, and possibly a warning should be emitted if the hooks are present.
There is no way to manually do an alias resolution with hooks for troubleshooting (other than sending an email, of course), which should also be fixed.
This is fixed in the next branch: chasquid-util now asks the running daemon to resolve the alias, so the answer will be authoritative and inclusive of any hooks.
This is forked from issue #17, where @DiederikvandenB reported that
chasquid-util aliases-resolve
does not take hooks into account, and that is confusing and misleading.At minimum, the documentation should mention this fact, and possibly a warning should be emitted if the hooks are present.
There is no way to manually do an alias resolution with hooks for troubleshooting (other than sending an email, of course), which should also be fixed.