[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#70077: An easier way to track buffer changes
From: |
Ihor Radchenko |
Subject: |
bug#70077: An easier way to track buffer changes |
Date: |
Mon, 01 Apr 2024 11:53:51 +0000 |
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> ... That's why `track-changes.el` bundles those into a single (BEG END
> BEFORE) change, which makes sure BEG/END are currently-valid buffer
> positions and thus easy to use.
> The previous buffer state is not directly available but can be
> easily reconstructed from (BEG END BEFORE).
Do I understand correctly that such bundling may result in a situation
when BEFORE is very long? In particular, I am thinking of a situation
when there are changes near the beginning and the end of buffer in quick
succession.
--
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#70077: An easier way to track buffer changes,
Ihor Radchenko <=
- bug#70077: An easier way to track buffer changes, Stefan Monnier, 2024/04/01
- bug#70077: An easier way to track buffer changes, Stefan Monnier, 2024/04/01
- bug#70077: An easier way to track buffer changes, Ihor Radchenko, 2024/04/02
- bug#70077: An easier way to track buffer changes, Stefan Monnier, 2024/04/02
- bug#70077: An easier way to track buffer changes, Ihor Radchenko, 2024/04/02
- bug#70077: An easier way to track buffer changes, Stefan Monnier, 2024/04/02
- bug#70077: An easier way to track buffer changes, Ihor Radchenko, 2024/04/03
- bug#70077: An easier way to track buffer changes, Stefan Monnier, 2024/04/03
- bug#70077: An easier way to track buffer changes, Ihor Radchenko, 2024/04/04