unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Kun Liu <kun.liu@gmail.com>, 42974@debbugs.gnu.org
Subject: bug#42974: 28.0.50; [feature/native-comp] keymap not currently defined in describe-mode result
Date: Fri, 21 Aug 2020 10:42:14 -0700	[thread overview]
Message-ID: <CADwFkmk6L=N-z+MDDh0dSCkgiTAemd1CZojENU5yBqwE_LPEmQ@mail.gmail.com> (raw)
In-Reply-To: <CA+Nei8Pbpgnmqig19wg5L6Mr0pei0gJbDEDPBW9qd2S=TOqRYg@mail.gmail.com>

Kun Liu <kun.liu@gmail.com> writes:

> As of commit c818c29771d3cb51875643b2f6c894073e429dd2, M-x m
> (describe-mode) does not show the key bindings.  Instead, it shows
> something like (in this case in shell mode) "Uses keymap
> ‘shell-mode-map’, which is not currently defined."

Just to confirm I'm seeing this as well.

To reproduce: (documentation 'c-mode)

In GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.22, cairo version 1.16.0)
 of 2020-08-17 built on joffe
Repository revision: 76faab27cf4055f6ac37b9b05c98bc03939afb7e
Repository branch: feature/native-comp
Windowing system distributor 'The X.Org Foundation', version 11.0.12008000
System Description: Debian GNU/Linux bullseye/sid

Configured using:
 'configure --with-nativecomp

Best regards,
Stefan Kangas





  reply	other threads:[~2020-08-21 17:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21 16:27 bug#42974: 28.0.50; [feature/native-comp] keymap not currently defined in describe-mode result Kun Liu
2020-08-21 17:42 ` Stefan Kangas [this message]
2020-08-30  8:30   ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-31 13:04     ` Stefan Kangas
2020-08-31 16:11       ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-24 14:16 ` Kun Liu

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='CADwFkmk6L=N-z+MDDh0dSCkgiTAemd1CZojENU5yBqwE_LPEmQ@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=42974@debbugs.gnu.org \
    --cc=kun.liu@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).