Daniel Mendler

Yes, the good thing here is that consult is not grabbing any keybindings by default. Choose what you like :)

@pavel-popov Thank you for the suggestion, but `consult-find-file` does not sound like a good fit for Consult. The improvements you have in mind cannot be solved on the level of...

@revrari I believe this issue is resolved?

What is missing to implement the use case described by @noctuid? It would be great if that would work. Is it possible that which-key shows the description? ~~~ elisp (define-key...

I understand that it is due to the restriction of describe-buffer-bindings. Would still be cool if there is additional support on top. My use case is a bit special: I...

> I think making describe-buffer-bindings aware of menu-item filters might be worth exploring. Which-key is not the only package that uses describe-buffer-bindings, so this may have beneficial effects for others...

@justbur What I wrote before: > There is still the which-key keymap based replacement infrastructure, maybe that could be leveraged to provide better descriptions for dynamically generated keymaps? I tried...

@justbur I got it to work by using the keymap based replacements! See https://github.com/minad/consult/blob/7cd2d40c131333d38787227cd62502cc6e991bea/consult.el#L393. I am pretty happy with this now and it works well. The only downside is that...

Would it make sense to apply the which-key-replacement-alist regexps afterwards?

I don't see the point. If the regexp-based replacement alist is short enough it does not matter if it is applied always. Most of the simple replacements can be done...