Ensure transient-current-* variables are unset on every exit

In the simple case, when `transient--post-command' determines that
the transient is being exited, it calls `transient--post-exit' to
unset internal state but takes care to unset `transient-current-*'
itself.

When the minibuffer is involved and for other recursive edits and
if an unexpected error occurs, it cannot take care of the latter.

In those cases we can do it in `transient--post-exit' instead, but
until now we didn't.  Do so if COMMAND is non-nil, which in the
normal case it is not.

Closes #323.

1 files changed, 6 insertions, 0 deletions

diff --git a/CHANGELOG b/CHANGELOG
index 4c23fbc..454ac36 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -12,6 +12,12 @@
   suffix command with the mouse, information about the command is now
   shown in the echo area or using a tooltip.  #282
 
+Bug fixes:
+
+- When the command that exits a transient uses the minibuffer,
+  ~transient-current-*~ variables were not immediately reset to
+  ~nil~. #323
+
 * v0.7.7    2024-10-04
 
 Bug fix: