From: ams@gnu.org (Alfred M. Szmidt)
To: Stefan Kangas <stefan@marxist.se>
Cc: justin@burkett.cc, emacs-devel@gnu.org
Subject: Re: Include which-key.el in the Emacs distribution
Date: Tue, 08 Sep 2020 12:22:30 -0400 [thread overview]
Message-ID: <E1kFgO6-0000cE-Dj@fencepost.gnu.org> (raw)
In-Reply-To: <CADwFkmmvVRqnQGA_d8bMA66SXbpjis+j-1UiceY7Lk7eY6iugA@mail.gmail.com> (message from Stefan Kangas on Tue, 8 Sep 2020 13:54:45 +0000)
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.
Could the output be improved though? The current output is VERY
verbose, and quite bare and unexplanatory. On my terminal it takes up
9 lines when just hitting C-x. It also dislikes any type of prefix
command and hides the output from those. E.g, C-h, M-o etc, where it
eats the message from the original command.
Instead why not if you press C-x in the echo area a short list of
commands could be produced that you can scroll through, similar to
which-key but not as talkative. It could say,
C-x (f - edit file, o - other window, ...)
The prefix commands C-x 4, C-x r etc could also produces such
messages. Like Emacs does for M-o. This list could be curated.
Maybe that would be a nice middle ground, not to talkative, helps the
new user and won't annoy the old farts too much?
next prev parent reply other threads:[~2020-09-08 16:22 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 [this message]
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=E1kFgO6-0000cE-Dj@fencepost.gnu.org \
--to=ams@gnu.org \
--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).