unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Corwin Brust <corwin@bru.st>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Include which-key.el in the Emacs distribution
Date: Sun, 13 Feb 2022 17:30:30 +0000	[thread overview]
Message-ID: <87wnhyk72h.fsf@posteo.net> (raw)
In-Reply-To: <CAJf-WoRaB428GBMGxdNW7i_AFp7cincWgZ78_iAcrvLjPGEsbA@mail.gmail.com> (Corwin Brust's message of "Fri, 11 Feb 2022 15:31:39 -0600")

Corwin Brust <corwin@bru.st> writes:

> On Tue, Sep 8, 2020 at 3:41 PM Stefan Kangas <stefan@marxist.se> wrote:
>>
>> Ergus <spacibba@aol.com> writes:
>>
>> > I really love which-key but enabling it by default for everyone could be
>> > a bit premature. Maybe adding a very easy to find option in the toolbar
>> > could be a better first step?
>> >
>> > So the ones (like me) who love it can improve it until it becomes ready
>> > to be default without the complains if the other who doesn't.
>>
>> Yes, we should definitely make any necessary improvements before
>> considering to make it the default.  I believe that's what Stefan M was
>> also arguing, so I see no disagreement on that point.
>>
>
> Hi all.  Having `which-key' available in core remains popular, at least on IRC.
>
> Now that it is available from GNU Elpa I wonder what is left to do and
> if there appears hope of including it with Emacs 29.

My first question is why it should be added to the core, given that it
can be installed with a single command OOTB?  My impression from using
(and seeing other people use) which-key would have me say that the UX it
provides goes contrary to the "style" that core functionality uses
traditionally (what other cases are there where not doing something
modifies the window configuration, the closes commonly used
functionality would be eldoc that displays information in the
minibuffer).

What I would be more interested in is to add optional support for C-h to
continue a command prefix, so that if I want to know what keys a keymap
provides, I can request it immediately without waiting for the idle
timer to trigger a often too small popup window, without loosing the
partial input.

-- 
	Philip Kaludercic



  reply	other threads:[~2022-02-13 17:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08 13:54 Include which-key.el in the Emacs distribution Stefan Kangas
2020-09-08 14:01 ` Ergus
2020-09-08 14:16   ` Stefan Kangas
2020-09-08 17:29   ` Yuan Fu
2020-09-08 17:40     ` Justin Burkett
2020-09-08 20:40       ` Stefan Kangas
2020-09-08 16:22 ` Alfred M. Szmidt
2020-09-08 17:24   ` Eli Zaretskii
2020-09-08 17:37     ` Amin Bandali
2020-09-08 17:51       ` Alfred M. Szmidt
2020-09-08 17:54         ` Justin Burkett
2020-09-08 18:06           ` Eli Zaretskii
2020-09-08 18:11             ` Justin Burkett
2020-09-08 20:40               ` Stefan Kangas
2020-09-08 18:10           ` Alfred M. Szmidt
2020-09-08 18:00       ` Eli Zaretskii
2020-09-08 19:12         ` Amin Bandali
2020-09-08 18:25 ` Caio Henrique
2020-09-08 19:19 ` Stefan Monnier
2020-09-08 20:14   ` Ergus
2020-09-08 20:40     ` Stefan Kangas
2022-02-11 21:31       ` Corwin Brust
2022-02-13 17:30         ` Philip Kaludercic [this message]
2022-02-14  9:04           ` Pankaj Jangid
2022-02-14 16:23           ` [External] : " Drew Adams
2022-02-14 22:09           ` Tim Cross
2022-02-13 17:59         ` Stephen Leake
2022-02-13 18:17           ` Corwin Brust
2022-02-13 23:25             ` Stephen Leake
2022-02-14  2:47               ` Stefan Monnier
2022-02-14  3:09                 ` Justin Burkett
2022-02-14  3:46                   ` Corwin Brust
     [not found] <<CADwFkmmvVRqnQGA_d8bMA66SXbpjis+j-1UiceY7Lk7eY6iugA@mail.gmail.com>
     [not found] ` <<E1kFgO6-0000cE-Dj@fencepost.gnu.org>
2020-09-08 17:55   ` Drew Adams
     [not found]   ` <<83sgbskwq8.fsf@gnu.org>
2020-09-08 18:05     ` Drew Adams

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87wnhyk72h.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=corwin@bru.st \
    --cc=emacs-devel@gnu.org \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).