Even better will be if there is some intermediate structured result which can be used by packages like which-key instead of parsing the string.
Andreas Schwab <schwab@linux-m68k.org> writes:
> The problem is that describe-buffer-bindings only changes the buffer to
> look up the bindings, but everything that generates the description
> (starting with describe-map-tree) doesn't know about that other buffer.
BTW, does anyone know why describe-map and describe-map-tree currently
inserts its result into buffer instead of just returning a string?