From: Eli Zaretskii <eliz@gnu.org>
To: <tomas@tuxteam.de>
Cc: rpluim@gmail.com, philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: master fa4203300fd: Merge remote-tracking branch 'origin/feature/which-key-in-core'
Date: Wed, 19 Jun 2024 17:41:13 +0300 [thread overview]
Message-ID: <865xu5ov06.fsf@gnu.org> (raw)
In-Reply-To: <ZnLfEPJzLmiicri6@tuxteam.de> (tomas@tuxteam.de)
> Date: Wed, 19 Jun 2024 15:37:20 +0200
> Cc: Robert Pluim <rpluim@gmail.com>, philipk@posteo.net,
> emacs-devel@gnu.org
> From: <tomas@tuxteam.de>
>
> On Wed, Jun 19, 2024 at 04:10:23PM +0300, Eli Zaretskii wrote:
>
> [...]
>
> > What's the downside of doing this unconditionally?
>
> You mean enabling "which-key" unconditionally?
No, showing keys from other maps. That's what you were suggesting to
have an option for, no? The option for turning on and off which-key
already exists, so discussing its necessity sounds redundant, no?
next prev parent reply other threads:[~2024-06-19 14:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171873998859.23986.6867742580209068033@vcs2.savannah.gnu.org>
[not found] ` <20240618194635.AC606C1FB66@vcs2.savannah.gnu.org>
2024-06-19 7:20 ` master fa4203300fd: Merge remote-tracking branch 'origin/feature/which-key-in-core' Robert Pluim
2024-06-19 7:42 ` Philip Kaludercic
2024-06-19 8:49 ` Robert Pluim
2024-06-19 12:01 ` Robert Pluim
2024-06-19 12:33 ` Stefan Kangas
2024-06-19 12:47 ` Robert Pluim
2024-06-19 13:00 ` Philip Kaludercic
2024-06-19 13:10 ` Eli Zaretskii
2024-06-19 13:32 ` Robert Pluim
2024-06-19 13:37 ` tomas
2024-06-19 13:43 ` Robert Pluim
2024-06-19 13:55 ` tomas
2024-06-19 14:41 ` Eli Zaretskii [this message]
2024-06-20 4:21 ` tomas
2024-06-19 11:57 ` Eli Zaretskii
2024-06-19 12:08 ` Robert Pluim
2024-06-24 19:25 ` Michael Albinus
2024-06-24 20:23 ` Philip Kaludercic
2024-06-25 6:37 ` Michael Albinus
2024-06-25 9:26 ` Philip Kaludercic
2024-06-25 10:04 ` Michael Albinus
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=865xu5ov06.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
--cc=rpluim@gmail.com \
--cc=tomas@tuxteam.de \
/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.