From: Gregor Zattler <telegraph@gmx.net>
To: Philip Kaludercic <philipk@posteo.net>, emacs-devel@gnu.org
Subject: Re: Adding a "quick-help" menu
Date: Sat, 17 Sep 2022 14:09:15 +0200 [thread overview]
Message-ID: <87o7ve19uc.fsf@no.workgroup> (raw)
In-Reply-To: <87mtaz44ka.fsf@posteo.net>
Hi Philip, emacs developers,
* Philip Kaludercic <philipk@posteo.net> [2022-09-16; 17:22 GMT]:
> Yes, but just like there is a difference between auto-completion and
> tab-completion, there is a difference to be considered here.
for me the main difference to all other help facilities is,
that there is zero cognitive burden: It only pops up when I
hit a prefix key and then don't know what to do.
It specifically shows help to this prefix key, I do not have
to move the mouse, I do not have to look for a symbol to
click or a menu entry which might be related.
I do not have to know how to bury or kill it, it does not
litter my buffer list with jet another buried buffer, it
does not permanently change my window configuration.
I think these are great features especially for newbies.
> Again, I don't think there is anything in Emacs by default that relies
> on non-input the way which-key does. One reason I dislike this is
> because I've seen how some people use `which-key-mode' in person, just
> waiting for the menu to (fragile) pop up, to skim through the columns to
> find what they are looking for. By comparison, I think that C-h and
> isearch/occur/etc. is more idiomatic.
But much more involved to use and they leave traces as
which-key does not.
> That being said, my proposal is much more modest, and has more to do
> with Nano's default help bar at the bottom of the screen.
My praise of which-key is in no way directed against your
proposal of a screen full of essential functions.
Ciao; Gregor
--
-... --- .-. . -.. ..--.. ...-.-
next prev parent reply other threads:[~2022-09-17 12:09 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 15:43 Adding a "quick-help" menu Philip Kaludercic
2022-09-16 16:11 ` Sean Whitton
2022-09-16 16:24 ` Stefan Kangas
2022-09-16 16:48 ` Philip Kaludercic
2022-09-16 17:03 ` Sławomir Grochowski
2022-09-16 17:22 ` Philip Kaludercic
2022-09-17 12:09 ` Gregor Zattler [this message]
2022-09-17 14:44 ` Philip Kaludercic
2022-09-17 17:48 ` Stefan Kangas
2022-09-17 21:45 ` Philip Kaludercic
2022-09-18 0:05 ` Stefan Kangas
2022-09-18 5:41 ` Eli Zaretskii
2022-09-18 9:10 ` Philip Kaludercic
2022-09-18 5:07 ` Visuwesh
2022-09-18 7:51 ` Gregor Zattler
2022-09-17 14:53 ` which-key (was: Adding a "quick-help" menu) Stefan Monnier
2022-09-18 5:12 ` which-key Visuwesh
2022-09-18 8:56 ` which-key Gregory Heytings
2022-09-18 8:58 ` which-key (was: Adding a "quick-help" menu) Gregory Heytings
2022-09-18 9:19 ` which-key Po Lu
2022-09-18 9:53 ` which-key Gregory Heytings
2022-09-18 10:10 ` which-key Lars Ingebrigtsen
2022-09-18 13:51 ` which-key Stefan Monnier
2022-09-18 15:39 ` which-key Stefan Kangas
2022-09-18 16:43 ` which-key Gregor Zattler
2022-09-18 16:49 ` which-key Gregory Heytings
2022-09-19 8:08 ` which-key Lars Ingebrigtsen
2022-09-19 8:19 ` which-key Gregory Heytings
2022-09-19 13:26 ` which-key Corwin Brust
2022-09-19 23:43 ` which-key Emanuel Berg
2022-09-19 8:06 ` which-key Lars Ingebrigtsen
2022-09-19 9:08 ` which-key Stefan Kangas
2022-09-18 11:09 ` which-key Po Lu
2022-09-17 16:47 ` [External] : Re: Adding a "quick-help" menu Drew Adams
2022-09-16 17:11 ` Stefan Kangas
2022-09-16 17:29 ` Philip Kaludercic
2022-09-16 17:38 ` [External] : " Drew Adams
2022-09-16 17:36 ` Drew Adams
2022-09-16 18:00 ` Stefan Monnier
2022-09-17 1:56 ` Po Lu
2022-09-16 21:03 ` Philip Kaludercic
2022-09-17 14:53 ` Philip Kaludercic
2022-09-17 1:54 ` Po Lu
2022-09-17 2:51 ` Stefan Kangas
2022-09-17 3:28 ` Stefan Monnier
2022-09-17 4:01 ` Visuwesh
2022-09-17 4:50 ` Po Lu
2022-09-17 4:48 ` Po Lu
2022-09-17 6:38 ` Stefan Kangas
2022-09-17 8:24 ` Po Lu
2022-09-17 8:49 ` Philip Kaludercic
2022-09-17 16:45 ` [External] : " Drew Adams
2022-09-17 17:36 ` Philip Kaludercic
2022-09-18 10:11 ` Lars Ingebrigtsen
2022-09-18 10:53 ` Philip Kaludercic
2022-09-18 17:03 ` Bob Rogers
2022-09-18 17:53 ` Philip Kaludercic
2022-09-18 19:25 ` Bob Rogers
2022-09-18 20:38 ` wilnerthomas--- via Emacs development discussions.
2022-09-18 21:21 ` Philip Kaludercic
2022-09-18 22:45 ` Christopher Dimech
2022-09-18 23:00 ` Philip Kaludercic
2022-09-19 1:40 ` Christopher Dimech
2022-09-19 7:54 ` Lars Ingebrigtsen
2022-09-19 8:26 ` Po Lu
2022-09-19 9:08 ` Stefan Kangas
2022-09-19 9:08 ` Stefan Kangas
2022-09-19 10:12 ` Philip Kaludercic
2022-10-13 14:30 ` Philip Kaludercic
2022-10-13 19:09 ` Lars Ingebrigtsen
2022-10-13 20:21 ` Philip Kaludercic
2022-10-14 11:03 ` Lars Ingebrigtsen
2022-10-14 7:30 ` Philip Kaludercic
2022-10-14 11:08 ` Lars Ingebrigtsen
2022-10-14 18:10 ` Philip Kaludercic
2022-10-16 0:29 ` Howard Melman
2022-10-16 16:01 ` Philip Kaludercic
2022-10-16 16:13 ` Howard Melman
2022-10-16 22:44 ` Philip Kaludercic
2022-10-17 1:00 ` Howard Melman
2022-10-17 1:00 ` [External] : " Drew Adams
2022-10-17 6:17 ` Eli Zaretskii
2022-10-17 6:29 ` Philip Kaludercic
2022-10-17 7:00 ` Eli Zaretskii
2022-10-17 7:12 ` Stefan Kangas
2022-10-17 15:32 ` Howard Melman
2022-10-17 5:10 ` Stefan Kangas
2022-10-17 6:31 ` Philip Kaludercic
2022-10-20 5:58 ` Protesilaos Stavrou
2022-10-20 6:37 ` Eli Zaretskii
2022-10-20 11:27 ` Philip Kaludercic
2022-10-20 12:51 ` Eli Zaretskii
2022-10-20 16:37 ` Philip Kaludercic
2022-10-20 16:39 ` Eli Zaretskii
2022-09-19 15:21 ` Howard Melman
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=87o7ve19uc.fsf@no.workgroup \
--to=telegraph@gmx.net \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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.