[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#65451: 30.0.50; `after-change-functions' are not triggered in the sa
From: |
Ihor Radchenko |
Subject: |
bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made |
Date: |
Fri, 25 Aug 2023 10:49:16 +0000 |
Eli Zaretskii <eliz@gnu.org> writes:
>> Then, treesit_record_change only uses byte positions. Will it be
>> possible to record buffer point positions, or may it be problematic?
>
> Sorry, I don't understand what you are saying here and how this is
> relevant to the issue at hand and to my comment in particular.
Never mind. I am jumping ahead of the discussion.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
- bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made, (continued)
- bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made, Eli Zaretskii, 2023/08/24
- bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made, Ihor Radchenko, 2023/08/24
- bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made, Eli Zaretskii, 2023/08/24
- bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made, Ihor Radchenko, 2023/08/24
- bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made, Eli Zaretskii, 2023/08/24
- bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made, Eli Zaretskii, 2023/08/25
- bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made, Ihor Radchenko, 2023/08/25
- bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made, Eli Zaretskii, 2023/08/26
- bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made, Ihor Radchenko, 2023/08/25
- bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made, Eli Zaretskii, 2023/08/25
- bug#65451: 30.0.50; `after-change-functions' are not triggered in the same order the changes are made,
Ihor Radchenko <=