On Wed, Apr 07, 2021 at 01:52:44PM +0100, Steve Karmeinsky wrote:
The only thing not working properly is setting the signature back to normal after replying to an alternate.
I didn't see how you overrode the signature, so I can only guess it's something like:
reply-hook . "set signature=~/.sig-default" reply-hook "~C alias1" "set signature=~/.sig-alias1" reply-hook "~C alias2" "set signature=~/.sig-alias2" ...It can be helpful to look at <http://www.mutt.org/doc/manual/#compose-flow> when adjusting these things. Looking at that, you can see reply-hooks fire first, then send-hooks, and then three steps below the message and signature are generated.
So, replies not covered by one of the aliases will set the signature back to default, but non-replies still need to reset back.send-hooks can use the pattern !~Q to be invoked in the non-reply case, so you could try adding:
send-hook !~Q "set signature=~/.sig-default" -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
