unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Justin Burkett <justin@burkett.cc>
To: Yuan Fu <casouri@gmail.com>
Cc: Ergus <spacibba@aol.com>, Stefan Kangas <stefan@marxist.se>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Include which-key.el in the Emacs distribution
Date: Tue, 8 Sep 2020 13:40:15 -0400	[thread overview]
Message-ID: <CAF5dqNJo_wY-kMKh3ELKViGL76-fp2kHSsXRJo0cSyeOor6djw@mail.gmail.com> (raw)
In-Reply-To: <F9B59028-F9C6-4A6E-9F50-6571D311185C@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

Hi Everyone,

I'm the author of which-key. For what it's worth, I have no doubt that the
package could be improved. I do have one idea off the top of my head for
how it could be more tightly integrated with emacs.

As far as the amount of output is concerned, it is possible to filter out
keys and customize the output to some degree. You can also limit the size
of the window and control sorting. Of course, emacs does actually have that
many bindings, and that may not be apparent to people unless they are
written out. The original idea was that there would be a significant delay,
so that you wouldn't see the window until you were "stuck".

In any event, I don't have a strong opinion on whether this should happen,
but I have time here and there to help.

Justin

On Tue, Sep 8, 2020 at 1:29 PM Yuan Fu <casouri@gmail.com> wrote:

>
>
> > On Sep 8, 2020, at 10:01 AM, Ergus <spacibba@aol.com> wrote:
> >
> > I can't support this more effusively!!
> >
> > +10 from my side.
>
>
>  +1 from me. Which-key could be helpful.
>
> Yuan
>

[-- Attachment #2: Type: text/html, Size: 1593 bytes --]

  reply	other threads:[~2020-09-08 17:40 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 [this message]
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
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=CAF5dqNJo_wY-kMKh3ELKViGL76-fp2kHSsXRJo0cSyeOor6djw@mail.gmail.com \
    --to=justin@burkett.cc \
    --cc=casouri@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=spacibba@aol.com \
    --cc=stefan@marxist.se \
    /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).