all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Kritixi Lithos <kritixilithos@gmail.com>
Cc: eliz@gnu.org, 38775@debbugs.gnu.org,
	Andreas Schwab <schwab@linux-m68k.org>
Subject: bug#38775: (kbd "C-x ( ... C-x )") gulps "C-x (" and "C-x )"
Date: Tue, 03 May 2022 16:21:50 +0200	[thread overview]
Message-ID: <87zgjywvb5.fsf@gnus.org> (raw)
In-Reply-To: <CADMw2zwCG8gA9Jt7mLjm4pzs=KiWcV6qt0PxJfem4=8R8Wbdbw@mail.gmail.com> (Kritixi Lithos's message of "Sat, 28 Dec 2019 21:36:34 +0200")

Kritixi Lithos <kritixilithos@gmail.com> writes:

> So how would you solve the original problem of calling emacs
> keystrokes with potential keyboard macros inside them?
> `command-execute` appears to use `execute-kbd-macro` according to the
> source, so trying `command-execute` on each keystroke does not work as
> intended with `C-x ( ... C-x )` among the commands.

I've now fixed this in Emacs 29.  `key-parse' now returns [24 40 4 24
41] for that sequence, while `kbd' maintains the backwards-compat code.
(This has been broken for half a year and nobody noticed -- in Emacs 29,
(kbd "C-x ( C-d C-x )") returned "" instead of "^D", so it's debatable
whether it makes sense to keep the compat code, but at least we do for
now.

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





  parent reply	other threads:[~2022-05-03 14:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-28 15:12 bug#38775: (kbd "C-x ( ... C-x )") gulps "C-x (" and "C-x )" Kritixi Lithos
2019-12-28 15:46 ` Andreas Schwab
2019-12-28 17:24   ` Eli Zaretskii
2019-12-28 19:36   ` Kritixi Lithos
2021-08-30  2:24     ` Lars Ingebrigtsen
2022-05-03 14:21     ` Lars Ingebrigtsen [this message]
2022-05-03 14:39       ` Kritixi Lithos
     [not found] <<783E4006-081B-404D-A606-30862A0BA1CF@gmail.com>
     [not found] ` <<87woagzc4u.fsf@igel.home>
     [not found]   ` <<83mubcnz16.fsf@gnu.org>
2019-12-28 18:22     ` 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

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

  git send-email \
    --in-reply-to=87zgjywvb5.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=38775@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=kritixilithos@gmail.com \
    --cc=schwab@linux-m68k.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 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.