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

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: casouri <at> gmail.com, 70077 <at> debbugs.gnu.org, yantar92 <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, phillip.lord <at> russet.org.uk, stephen_leake <at> stephe-leake.org, alan.zimm <at> gmail.com, monnier <at> iro.umontreal.ca
Subject: bug#70077: An easier way to track buffer changes
Date: Sat, 30 Mar 2024 16:31:56 +0300

> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: 70077 <at> debbugs.gnu.org, casouri <at> gmail.com, yantar92 <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, monnier <at> iro.umontreal.ca, phillip.lord <at> russet.org.uk
> Date: Sat, 30 Mar 2024 13:19:31 +0000
> 
> Looking at the implementation of `track-changes--before/after', I can
> see that it is updating the BEFORE string and these updates implicitly
> assume that the changes arrive in order - which is not true in some edge
> cases described in the bug report.

So I guess you have detected a bug in the implementation before it was
even finalized and installed.

Previous Next

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