From: "João Távora" <joaotavora@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 72696@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Dario Gjorgjevski <dario.gjorgjevski@gmail.com>
Subject: bug#72696: Track-changes errors out when file is overwritten using Node.js's fs.writeFile (at least on macOS)
Date: Thu, 19 Sep 2024 22:47:14 +0100 [thread overview]
Message-ID: <CALDnm51+2Ducxpe8S6b3Qificvshat_y7qT7ec4J=yzeiVLhZA@mail.gmail.com> (raw)
In-Reply-To: <jwvbk0j9523.fsf-monnier+emacs@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.
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.
João
next prev parent reply other threads:[~2024-09-19 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 10:58 bug#72696: Track-changes errors out when file is overwritten using Node.js's fs.writeFile (at least on macOS) Dario Gjorgjevski
2024-08-18 11:02 ` Eli Zaretskii
2024-08-18 16:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-18 20:36 ` Dario Gjorgjevski
2024-08-20 12:15 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-22 11:19 ` Dario Gjorgjevski
2024-08-22 11:27 ` Dario Gjorgjevski
2024-09-07 7:15 ` Eli Zaretskii
2024-09-08 23:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-18 22:02 ` Dario Gjorgjevski
2024-09-19 5:32 ` Eli Zaretskii
2024-09-19 12:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-19 21:47 ` João Távora [this message]
2024-09-20 6:21 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALDnm51+2Ducxpe8S6b3Qificvshat_y7qT7ec4J=yzeiVLhZA@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=72696@debbugs.gnu.org \
--cc=dario.gjorgjevski@gmail.com \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).