bug#72696: Track-changes errors out when file is overwritten using Node.js's fs.writeFile (at least on macOS)

[Eli Zaretskii <eliz@gnu.org>]

> From: João Távora <joaotavora@gmail.com>
> Date: Thu, 19 Sep 2024 22:47:14 +0100
> Cc: Eli Zaretskii <eliz@gnu.org>, Dario Gjorgjevski <dario.gjorgjevski@gmail.com>, 72696@debbugs.gnu.org
> 
> On Thu, Sep 19, 2024 at 1:58 PM Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> >
> > > João, is Stefan's patch okay with you?  AFAIU, the same problem exists
> > > on the emacs-30 release branch, so I'd like to install the patch
> > > there, if you agree.
> >
> > Indeed, it belongs there.
> > It should have been part of the original commit d7a83e23d47c.
> 
> You can go ahead and merge it.  I dont' know what it does
> but i trust Stefan.

Thanks.  Stefan, please install on the emacs-30 branch.

> Although I have to say that on the topic of synchronization failures
> between Eglot and servers, I'm not sure that things have improved
> much since this new layer of abstraction was added.  By "I'm not
> sure" I really mean that.  Maybe pre-existing failures are just more
> visible right now (because the new code warns and logs them), but
> I have a nagging feeling that there are more of them.  No hard
> proof though.
> 
> I also half-expected things to get fixed in Emacs proper, using
> Eglot as testing bed, but I'm not sure that has happened either.
> Anyway this is just a comment.

I agree with your general feeling, and I think this case might belong
to those pre-existing failures which track-changes uncovers.