unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 57529@debbugs.gnu.org
Subject: bug#57529: 28.1; `C-c C-x' prefix key and keymap, `C-c C-x C-h'
Date: Thu, 1 Sep 2022 18:05:46 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488869632A6972DAFDB1A68F37B9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)

Dunno, but this seems like a bug (you decide):

https://emacs.stackexchange.com/q/73390/

`C-c' is a prefix key bound to `mode-specific-map', but it seems to be
set up in C source code.  `C-c C-x' is apparently defined (unlike, say,
`C-c C-x 4') as a prefix key, but it's not clear what its keymap is (and
it's apparently empty by default).

Dunno what changes should be made, to make clear to users what the story
is - why, for example, `C-c C-x' just waits for another key, even though
there's no such key defined in the keymap.

Maybe this is a more general "problem", for empty prefix keys?  Or is it
a result of the prefix being defined in C?

In GNU Emacs 28.1 (build 2, x86_64-w64-mingw32)
 of 2022-04-21 built on AVALON
Windowing system distributor 'Microsoft Corp.', version 10.0.19044
System Description: Microsoft Windows 10 Pro (v10.0.2009.19044.1889)

Configured using:
 'configure --with-modules --without-dbus --with-native-compilation
 --without-compress-install CFLAGS=-O2'

Configured features:
ACL GIF GMP GNUTLS HARFBUZZ JPEG JSON LCMS2 LIBXML2 MODULES NATIVE_COMP
NOTIFY W32NOTIFY PDUMPER PNG RSVG SOUND THREADS TIFF TOOLKIT_SCROLL_BARS
XPM ZLIB

(NATIVE_COMP present but libgccjit not available)

Important settings:
  value of $LANG: ENU
  locale-coding-system: cp1252






             reply	other threads:[~2022-09-01 18:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 18:05 Drew Adams [this message]
2022-09-01 18:42 ` bug#57529: 28.1; `C-c C-x' prefix key and keymap, `C-c C-x C-h' Eli Zaretskii
2022-09-01 19:07   ` Drew Adams

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=SJ0PR10MB5488869632A6972DAFDB1A68F37B9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=57529@debbugs.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).