From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: felician.nemeth@gmail.com, kby@tilde.team, 61478@debbugs.gnu.org
Subject: bug#61478: 28.2; eglot keeps sending `didSave` notifications despite the active server not supporting `textDocumentSync`
Date: Tue, 14 Feb 2023 15:59:50 +0200 [thread overview]
Message-ID: <83wn4kcppl.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm51eF1VdOPH5DWf23tdJByvOTq65FTX1kWAe5+a=hbokJg@mail.gmail.com> (message from João Távora on Tue, 14 Feb 2023 12:57:35 +0000)
> From: João Távora <joaotavora@gmail.com>
> Date: Tue, 14 Feb 2023 12:57:35 +0000
> Cc: kby@tilde.team, Felician Nemeth <felician.nemeth@gmail.com>, 61478@debbugs.gnu.org
>
> ENOPATCH
>
> Probably no need for copyright assignment, but I need to see the
> changes.
>
> I don't understand, i see a didSave.patch file attached to to kby's mail to this bug. That's the (trivial) patch I'm
> referring to. Can't you see it, Eli?
You mean, the one here:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61478#17
? I received this message after receiving and answering yours.
If that is the patch, it is OK, but please remember a proper commit
log message, which mentions the bug number and includes the
Copyright-paperwork-exempt thingy.
Thanks.
next prev parent reply other threads:[~2023-02-14 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 14:52 bug#61478: 28.2; eglot keeps sending `didSave` notifications despite the active server not supporting `textDocumentSync` ~kby via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-13 18:30 ` Felician Nemeth
2023-02-13 18:44 ` João Távora
2023-02-13 19:00 ` ~kby via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-13 23:50 ` João Távora
2023-02-14 12:01 ` Eli Zaretskii
2023-02-14 12:57 ` João Távora
2023-02-14 13:59 ` Eli Zaretskii [this message]
2023-02-14 14:12 ` João Távora
2023-02-14 14:40 ` Eli Zaretskii
2023-02-14 23:34 ` João Távora
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wn4kcppl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61478@debbugs.gnu.org \
--cc=felician.nemeth@gmail.com \
--cc=joaotavora@gmail.com \
--cc=kby@tilde.team \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.