unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56210@debbugs.gnu.org, rhansen@rhansen.org
Subject: bug#56210: 29.0.50; Keyboard macros do not trigger after-change-functions
Date: Tue, 28 Jun 2022 14:26:30 +0200	[thread overview]
Message-ID: <875yklrn2h.fsf@gnus.org> (raw)
In-Reply-To: <83mtdx6kt5.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 28 Jun 2022 15:20:54 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> I didn't write that code, and have no sentiments for it (although I
> generally assume that all the temporary buffers disable such hooks for
> performance reasons).  I just explained what Richard saw, and it took
> me some non-trivial time.
>
> Maybe we should modify with-current-buffer-window to not have such
> global effects on the body?

I think that would be good, but somebody should investigate why whoever
added that binding in temp-buffer-window-setup did it in the first
place.  Perhaps there's some obscure reason why it makes sense -- it's
not at all obvious to me.

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





  reply	other threads:[~2022-06-28 12:26 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
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 [this message]
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=875yklrn2h.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).