From: Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org>
To: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Ideas to improve the output of C-h m?
Date: Sat, 2 May 2020 13:05:52 +0900 [thread overview]
Message-ID: <2B19BBD2-04B4-4137-A2DD-CCD2C7A87178@traduction-libre.org> (raw)
In-Reply-To: <DB7PR03MB47008BFEC533E83CF9548E00EEAB0@DB7PR03MB4700.eurprd03.prod.outlook.com>
> On May 1, 2020, at 23:34, Clément Pit-Claudel <clement.pitclaudel@live.com> wrote:
>
> Hi all,
>
> A while ago I tried to improve the discoverability of the keybindings of one of my packages by writing an enhanced version of the keybindings part of C-h m. The idea was to list keybindings along with the first line of their docstrings, instead of just listing the name of the function.
This discussion, along with the one about transient about mode remind me of what which-key and helpful do. Those are not perfect solutions but they are pretty good considering the state of affairs in terms of discoverability.
Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune
prev parent reply other threads:[~2020-05-02 4:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 14:34 Ideas to improve the output of C-h m? Clément Pit-Claudel
2020-05-01 15:55 ` Stefan Monnier
2020-05-01 16:16 ` Clément Pit-Claudel
2020-05-01 17:44 ` Stefan Monnier
2020-05-01 23:02 ` Stefan Kangas
2020-05-02 3:24 ` Clément Pit-Claudel
2020-05-06 13:34 ` Stefan Kangas
[not found] ` <jwv5zd9wyj6.fsf-monnier+emacs@gnu.org>
[not found] ` <CADwFkmmhezor_jCwff8YH2wVvnyb7Rf=7YnLeeN_aRehkw8beA@mail.gmail.com>
2020-08-21 0:27 ` scratch/substitute-command-keys: C conversion of s-c-k Stefan Kangas
2020-05-03 3:39 ` Ideas to improve the output of C-h m? Richard Stallman
2020-05-02 4:05 ` Jean-Christophe Helary [this message]
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=2B19BBD2-04B4-4137-A2DD-CCD2C7A87178@traduction-libre.org \
--to=jean.christophe.helary@traduction-libre.org \
--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).