all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Justin Burkett <justin@burkett.cc>
To: Robert Pluim <rpluim@gmail.com>
Cc: 71648@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>, jb@jeremybryant.net
Subject: bug#71648: 30.0.50; Allow which-key to report on translation bindings
Date: Thu, 20 Jun 2024 10:20:36 -0400	[thread overview]
Message-ID: <CAF8XuLhBdKt_UnSG_6-8nE9pt6GZmikodQK3FJsU-n-tN7xSBg@mail.gmail.com> (raw)
In-Reply-To: <87v824vx14.fsf@gmail.com>

On Thu, Jun 20, 2024 at 4:27 AM Robert Pluim <rpluim@gmail.com> wrote:
>
> >>>>> On Wed, 19 Jun 2024 11:48:01 -0400, Justin Burkett <justin@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.

I can see an argument for either. My only concern with the option
would be explaining what the option does in plain language.

>
> Robert
> --





  reply	other threads:[~2024-06-20 14:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 12:04 bug#71648: 30.0.50; Allow which-key to report on translation bindings Robert Pluim
2024-06-19 13:12 ` Eli Zaretskii
2024-06-19 15:09   ` Justin Burkett
2024-06-19 15:16     ` Robert Pluim
2024-06-19 15:42       ` Justin Burkett
2024-06-19 21:13       ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 15:34     ` Eli Zaretskii
2024-06-19 15:48       ` Justin Burkett
2024-06-20  8:27         ` Robert Pluim
2024-06-20 14:20           ` Justin Burkett [this message]
2024-06-20 14:56             ` Robert Pluim
2024-06-20 15:40               ` Justin Burkett
2024-06-24 13:14                 ` Robert Pluim
2024-06-24 13:30                   ` Eli Zaretskii
2024-06-24 17:20                     ` Robert Pluim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAF8XuLhBdKt_UnSG_6-8nE9pt6GZmikodQK3FJsU-n-tN7xSBg@mail.gmail.com \
    --to=justin@burkett.cc \
    --cc=71648@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=rpluim@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.