GNU bug report logs -
#71648
30.0.50; Allow which-key to report on translation bindings
Previous Next
Reported by: Robert Pluim <rpluim <at> gmail.com>
Date: Wed, 19 Jun 2024 12:05:02 UTC
Severity: normal
Tags: fixed
Found in version 30.0.50
Fixed in version 30.1
Done: Robert Pluim <rpluim <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
On Thu, Jun 20, 2024 at 10:56 AM Robert Pluim <rpluim <at> gmail.com> wrote:
>
> >>>>> On Thu, 20 Jun 2024 10:20:36 -0400, Justin Burkett <justin <at> burkett.cc> said:
>
> Justin> On Thu, Jun 20, 2024 at 4:27 AM Robert Pluim <rpluim <at> gmail.com> wrote:
> >>
> >> >>>>> On Wed, 19 Jun 2024 11:48:01 -0400, Justin Burkett <justin <at> burkett.cc> said:
> >>
> Justin> In any event, Robert's example was helpful, and I think that
> Justin> information would be useful to include in which-key.
> >>
> >> By default, or with a custom option? If the latter, it could be a list
> >> of 'extra' keymaps for `which-key' to consult.
>
> Justin> I can see an argument for either. My only concern with the option
> Justin> would be explaining what the option does in plain language.
>
> Wordsmithing is easy ;-)
>
> (defcustom which-key-extra-keymaps nil
> "List of extra keymaps to show bindings from.
> This allows you to add personal keymaps for `which-key' to check. A
> preset value is available to enable looking in `key-translation-map',
> which contains the \\='C-x 8' bindings for entering common characters."
> :type '(choice (list :tag "Translation map" (const key-translation-map))
> (repeat :tag "Custom" symbol))
> :version "30.1")
>
That seems reasonable enough. How about doing both? Add the option and
use key-translation-map for the default value.
> Robert
> --
This bug report was last modified 328 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.