Daniel Mendler

If you want to keep this behavior as is, is it possible to replace both key and command? Somehow like this: ~~~ elisp (which-key-add-keymap-based-replacements ctl-x-map "RET" '("⏎" . "encoding") ...)...

I am thinking about another solution for the issue: * Always apply first the keymap and then the regexp based lookup. * Count the number of iteration steps regarding regexp...

@noctuid Do you plan to add the `completing-read` interface to link-hint? It is quite useful also in combination with `embark-collect`.

Interesting, I was not aware of `ffap-menu`. But a link-hint `completing-read` interface should be more general? cc @oantolin

> It turns out minibuffer buffers are reused. Seems a bit nuts, but that's how it is. Unfortunately, this means the post-command-hook registered by this library sticks around. No, this...

> So the minibuffer is reused, but there's was a bug in kill-all-local-variables Okay, it seems like it. This is nonsense. At least the cleanup is fixed now.

I would like to have C-g to always stop. Then we could even remove the STOP actions from the frontends.

Maybe I will send a PR (no promises!), but with my PR #94 I am already very happy with the functionality offered by your package :)

> 1. If you quit an export, you can no longer export as usual without > vertico reappearing and forcing you to select an entry. I don't see this in...

> I bet I know what it is: the dired buffer is probably reverting itself, and Embark abuses the revert-buffer-function for its "revert-as-rerun" functionality. Makes sense. Maybe Embark should set...