GNU bug report logs - #78042
31.0.50; Improper sequence of `before/after-change-functions` calls

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 78042 <at> debbugs.gnu.org
Subject: Re: bug#78042: 31.0.50; Improper sequence of
 `before/after-change-functions` calls
Date: Sat, 26 Apr 2025 09:22:32 +0300

> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: 78042 <at> debbugs.gnu.org
> Date: Fri, 25 Apr 2025 15:12:18 -0400
> 
> >> There is currently no attempt in the C code to solve this "by
> >> construction" or "by design".  Instead we fix the offenders as we bump
> >> into them.
> > I submit that we will never be able to solve all of them.
> 
> I'm pretty sure we can solve all the ones we find.
> But we may never find them all, indeed.
> 
> My request for comments/objection was not about whether it is worth
> fixing this bug (there is no doubt about that on my side: it affects at
> least Eglot and CC-mode), but whether the approach I used is acceptable
> or if you have a better alternative to propose.

The only alternative I can think of is to be able to handle nested
notifications, such as what happens in this case, as correct.  What
are the problems due to which we must have paired notifications
without nesting?

Previous Next

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