unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
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 10:56:01 +0200	[thread overview]
Message-ID: <87pnixxe5a.fsf@web.de> (raw)
In-Reply-To: <87a7a1pjb6.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 16 Oct 2019 03:31:41 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> 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?

Why would they?  This char syntax is widely used.

> And no matter how you display the keymap in `C-h v', it's going to be
> pretty incomprehensible.

We have just very different opinions here I think.

Michael.





      reply	other threads:[~2019-10-16  8:56 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
2019-10-16  8:56             ` Michael Heerdegen [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=87pnixxe5a.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=25174@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=larsi@gnus.org \
    --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).