From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>,
25174@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#25174: C-h v some keymap now gives some numbers instead of the familiar bindings
Date: Wed, 16 Oct 2019 03:31:41 +0200 [thread overview]
Message-ID: <87a7a1pjb6.fsf@gnus.org> (raw)
In-Reply-To: <878spmz9yx.fsf@web.de> (Michael Heerdegen's message of "Tue, 15 Oct 2019 10:31:02 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> A keymap is just a list (or vector); C-h v should display it as is.
>
> It would display it "as is", it would just use a syntax like e.g. ?t
> instead of 166. How would that be problematic?
I think it just sounds a bit confusing. Would users believe that ?t is
something else than 166 just in a keymap context? And no matter how you
display the keymap in `C-h v', it's going to be pretty incomprehensible.
But there's also a parallel bug report about adding a describe-keymap
command that'll display the keymap in a more sensible fashion (not as a
list/vector at all), and that's probably going to be merged.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-16 1:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 18:17 bug#25174: C-h v some keymap now gives some numbers instead of the familiar bindings 積丹尼 Dan Jacobson
2016-12-13 4:03 ` npostavs
2016-12-13 5:58 ` 積丹尼 Dan Jacobson
2019-10-14 19:42 ` Lars Ingebrigtsen
2019-10-14 20:09 ` Michael Heerdegen
2019-10-14 20:12 ` Lars Ingebrigtsen
2019-10-15 8:31 ` Michael Heerdegen
2019-10-16 1:31 ` Lars Ingebrigtsen [this message]
2019-10-16 8:56 ` Michael Heerdegen
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=87a7a1pjb6.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=25174@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=michael_heerdegen@web.de \
--cc=npostavs@users.sourceforge.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 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).