From: Ergus <spacibba@aol.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel@gnu.org, Justin Burkett <justin@burkett.cc>
Subject: Re: Include which-key.el in the Emacs distribution
Date: Tue, 8 Sep 2020 16:01:55 +0200 [thread overview]
Message-ID: <20200908140155.4q4ujygprhevby7b@Ergus> (raw)
In-Reply-To: <CADwFkmmvVRqnQGA_d8bMA66SXbpjis+j-1UiceY7Lk7eY6iugA@mail.gmail.com>
I can't support this more effusively!!
+10 from my side.
What I don't understand is why the version in elpa is very old (and says
obsolete) compared to the one in melpa.
On Tue, Sep 08, 2020 at 01:54:45PM +0000, Stefan Kangas wrote:
>Dear all,
>
>`which-key' is a package that unobtrusively shows you the available
>keybindings at the bottom of the screen upon typing a prefix command
>(after a configurable delay). It is an excellent alternative and
>complement to the default help. See the screenshot here:
>
> https://raw.githubusercontent.com/justbur/emacs-which-key/master/img/which-key-bottom.png
>
>`which-key' is in GNU ELPA, and was upgraded yesterday:
>
> https://elpa.gnu.org/packages/which-key.html
>
>I propose to include `which-key' in the default Emacs distribution.
>I expect that it will be extremely useful for beginning users, but it also
>helps advanced users to quickly look up and discover keybindings. In my
>experience, that is true even in modes you already know deeply.
>
>I've proposed this before, and have not seen any objections so far.
>So I'd like to ask here again, to see if people have any concerns or
>pointers for how to go about it in practice.
>
>Any comments?
>
>Best regards,
>Stefan Kangas
>
>PS. I personally think it should be enabled by default, but we would
> probably do better to first include it as an option for people to
> get more experience with it.
>
next prev parent reply other threads:[~2020-09-08 14:01 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 [this message]
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
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=20200908140155.4q4ujygprhevby7b@Ergus \
--to=spacibba@aol.com \
--cc=emacs-devel@gnu.org \
--cc=justin@burkett.cc \
--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).