all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Teika Kazura <teika@gmx.com>
Cc: 55607@debbugs.gnu.org
Subject: bug#55607: 28.1; C-x is hardcoded, but should use the keymap ctl-x-map
Date: Wed, 25 May 2022 03:50:54 +0200	[thread overview]
Message-ID: <871qwifkht.fsf@gnus.org> (raw)
In-Reply-To: <20220524.152211.1734534619486113978.teika@gmx.com> (Teika Kazura's message of "Tue, 24 May 2022 15:22:11 +0900 (JST)")

Teika Kazura <teika@gmx.com> writes:

> At least in the file emacs-28.1/lisp/emacs-lisp/edebug.el, the prefix
> key C-x is hardcoded. An error will be produced if you bind C-x to
> something else.  Instead `ctl-x-map' should be respected.
>
> How to reproduce it:
> $ emacs -Q -l foo.el
> ------------------------------------------------------------------------
>
> The content of foo.el:
> ------------------------------------------------------------------------
> (setq debug-on-error t)
> (global-set-key "\C-x" 'fill-paragraph) ; or whatever
> (require 'edebug)
> ------------------------------------------------------------------------

[...]

> Another minor issue: In edebug.el, the lines 43-44 read:
> ------------------------------------------------------------------------
> ;; If you wish to change the default edebug global command prefix, change:
> ;; (setq global-edebug-prefix "\C-xX")
> ------------------------------------------------------------------------
> but `global-edebug-prefix' is obsolete since 28.1 .

I've now fixed this in Emacs 29.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-05-25  1:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  6:22 bug#55607: 28.1; C-x is hardcoded, but should use the keymap ctl-x-map Teika Kazura
2022-05-25  1:50 ` Lars Ingebrigtsen [this message]
2022-05-25 12:12   ` Teika Kazura

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871qwifkht.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=55607@debbugs.gnu.org \
    --cc=teika@gmx.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.