bug#46982: 28.0.50; after-change-functions in an indirect buffer are not

bug-gnu-emacs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#46982: 28.0.50; after-change-functions in an indirect buffer are not

From:	Stefan Monnier
Subject:	bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa)
Date:	Tue, 21 Jun 2022 16:21:09 -0400
User-agent:	Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux)

> It might be a good thing to mention somewhere around
> `clone-buffer`, yes.  I'll see what I can come up with.

Hmm... we don't document `clone-buffer` anywhere that I can see.
Any suggestion where I could put that kind of info?


        Stefan

[Prev in Thread]

Current Thread

[Next in Thread]

bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa), Stefan Monnier, 2022/06/16
- bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa), Eli Zaretskii, 2022/06/17
  - bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa), Stefan Monnier, 2022/06/17
    - bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa), Eli Zaretskii, 2022/06/17
    - bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa), Stefan Monnier <=
    - bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa), Ihor Radchenko, 2022/06/21
    - bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa), Eli Zaretskii, 2022/06/21
    - bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa), Stefan Monnier, 2022/06/29
    - bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa), Eli Zaretskii, 2022/06/29
    - bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa), Stefan Monnier, 2022/06/29
    - bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa), Eli Zaretskii, 2022/06/29
    - bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa), Stefan Monnier, 2022/06/29
    - bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa), Stefan Monnier, 2022/06/22

Prev by Date: bug#56116: Feature: new Tetris randomizer
Next by Date: bug#45898: 27.1; wedged in redisplay again
Previous by thread: bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa)
Next by thread: bug#46982: 28.0.50; after-change-functions in an indirect buffer are not called if the change is done while base buffer is active (and vice versa)
Index(es):
- Date
- Thread