unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Hansen <rhansen@rhansen.org>
Cc: 56210@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#56210: 29.0.50; Keyboard macros do not trigger after-change-functions
Date: Mon, 27 Jun 2022 09:50:50 +0200	[thread overview]
Message-ID: <87mtdy8rz9.fsf@gnus.org> (raw)
In-Reply-To: <70bed502-1c51-8cd6-68b1-16c4e3c410e0@rhansen.org> (Richard Hansen's message of "Sun, 26 Jun 2022 23:21:24 -0400")

Richard Hansen <rhansen@rhansen.org> writes:

> I changed the test to switch to the temporary buffer in the selected
> window and it now reliably inserts "x" into the temporary buffer.  It
> still doesn't run the `after-change-functions' hook, however.  Updated
> test code:

It's pretty mysterious -- but does the same thing happen if you execute
a keyboard macro interactively?  Or if you run the same code outside of
an ert context?

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





  reply	other threads:[~2022-06-27  7:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-25  6:21 bug#56210: 29.0.50; Keyboard macros do not trigger after-change-functions Richard Hansen
2022-06-25 11:51 ` Lars Ingebrigtsen
2022-06-25 18:06   ` Richard Hansen
2022-06-25 18:56     ` Eli Zaretskii
2022-06-25 20:34       ` Richard Hansen
2022-06-26  8:10         ` Eli Zaretskii
2022-06-27  3:21           ` Richard Hansen
2022-06-27  7:50             ` Lars Ingebrigtsen [this message]
2022-06-27 16:52               ` Richard Hansen
2022-06-27 16:54             ` Eli Zaretskii
2022-06-27 17:07               ` Richard Hansen
2022-06-27 17:17                 ` Eli Zaretskii
2022-06-27 17:22                   ` Richard Hansen
2022-06-28 11:31                   ` Lars Ingebrigtsen
2022-06-28 12:20                     ` Eli Zaretskii
2022-06-28 12:26                       ` Lars Ingebrigtsen
2022-06-27 17:23                 ` Richard Hansen
2022-06-29 23:17               ` Richard Hansen

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=87mtdy8rz9.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=56210@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rhansen@rhansen.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).