[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: |
Eli Zaretskii |
|
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: |
Wed, 22 Jun 2022 05:36:00 +0300 |
> From: Ihor Radchenko <yantar92@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 46982@debbugs.gnu.org
> Date: Wed, 22 Jun 2022 07:29:05 +0800
>
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> >> 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?
>
> `clone-indirect-buffer' I think. For example, in 19.6 Indirect Buffers
> section of the manual.
Yes, there, please.
- 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, 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), 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 <=
- 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