GNU bug report logs - #70077
An easier way to track buffer changes

Previous Next

Full log

Message #59 received at 70077 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: yantar92 <at> posteo.net, 70077 <at> debbugs.gnu.org, casouri <at> gmail.com,
 qhong <at> alum.mit.edu, frederic.bour <at> lakaban.net, joaotavora <at> gmail.com,
 mail <at> nicolasgoaziou.fr, acm <at> muc.de, stephen_leake <at> stephe-leake.org,
 alan.zimm <at> gmail.com, phillip.lord <at> russet.org.uk
Subject: Re: bug#70077: An easier way to track buffer changes
Date: Sat, 30 Mar 2024 19:45:02 +0300

> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: 70077 <at> debbugs.gnu.org,  mail <at> nicolasgoaziou.fr,  yantar92 <at> posteo.net,
>   acm <at> muc.de,  joaotavora <at> gmail.com,  alan.zimm <at> gmail.com,
>   frederic.bour <at> lakaban.net,  phillip.lord <at> russet.org.uk,
>   stephen_leake <at> stephe-leake.org,  casouri <at> gmail.com,  qhong <at> alum.mit.edu
> Date: Sat, 30 Mar 2024 10:58:40 -0400
> 
> > Otherwise, the above looks like doing all the job in
> > after-change-functions, and it is not clear to me how is that better,
> > since if track-changes-fetch will fetch a series of changes,
> 
> `track-changes-fetch` will call its function argument only once.
> If several changes happened since last time, `track-changes.el` will
> summarize them into a single (BEG END BEFORE).

Then I don't think you will be able to guarantee that in all cases.
You are basically trying to solve a problem that many packages which
used the modification hooks tried to solve, but where they relied on
some specifics of the problem they wanted to solve, you are trying to
solve it in general, and I just don't believe it's possible (but will
be happy to learn I'm mistaken).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.