From: Juri Linkov <juri@linkov.net>
To: Robert Pluim <rpluim@gmail.com>
Cc: 74903@debbugs.gnu.org, Mekeor Melire <mekeor@posteo.de>,
Stefan Kangas <stefankangas@gmail.com>,
Eli Zaretskii <eliz@gnu.org>, Andrea Corallo <acorallo@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#74903: [PATCH] Add function to show table of keys when describing keymap variable
Date: Tue, 17 Dec 2024 09:59:57 +0200 [thread overview]
Message-ID: <877c7yg2e2.fsf@mail.linkov.net> (raw)
In-Reply-To: <87ttb24ul4.fsf@gmail.com> (Robert Pluim's message of "Tue, 17 Dec 2024 08:49:59 +0100")
> Mekeor> 1. Allow users to opt-in to have C-h v foo-keymap RET show a table of
> Mekeor> key bindings in addition to the formatting as S-expression. This fits
> Mekeor> well into the existing help-fns mechanism. The patch I submitted
> Mekeor> implements a prototype.
>
> Again, I donʼt see a need for it. A user trying to figure out
> keybindings is not going to be inspecting keymap variables, and
> `describe-bindings' or `describe-mode' tells them what they need to
> know. A developer writing code presumably knows about keymaps, and
> doesnʼt need a different visual representation of them to get stuff
> done.
It would be nice if users will be able first to see keymap tables
in the output of `describe-repeat-maps', then click on a map
variable, and see the same keymap table individually.
next prev parent reply other threads:[~2024-12-17 7:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-15 23:14 bug#74903: [PATCH] Add function to show table of keys when describing keymap variable Mekeor Melire
2024-12-16 15:57 ` Eli Zaretskii
2024-12-16 17:28 ` Robert Pluim
2024-12-16 18:41 ` Mekeor Melire
2024-12-17 3:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-17 7:49 ` Robert Pluim
2024-12-17 7:59 ` Juri Linkov [this message]
2024-12-17 8:32 ` Robert Pluim
2024-12-17 19:00 ` Juri Linkov
2024-12-18 12:04 ` Robert Pluim
2024-12-18 17:28 ` Juri Linkov
2024-12-17 2:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-18 0:21 ` Mekeor Melire
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=877c7yg2e2.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=74903@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=mekeor@posteo.de \
--cc=monnier@iro.umontreal.ca \
--cc=rpluim@gmail.com \
--cc=stefankangas@gmail.com \
/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).