From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
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 14:12:23 +0000 [thread overview]
Message-ID: <87pmactjy0.fsf@gmail.com> (raw)
In-Reply-To: <83wn4kcppl.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 14 Feb 2023 15:59:50 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
Odd, as the one you got earlier was a reply to the one you got later. An
EOUTOFORDER somewhere (probably due to moderation?)
> 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.
Yep, I'll provide that. It's 'Copyright-paperwork-exempt: Yes' in its
own line, I think.
Regarding the "kby <kby@tilde.team>" author. Kby is there any better
name? Eli, are these obscure names OK as well?
João
next prev parent reply other threads:[~2023-02-14 14:12 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
2023-02-14 14:12 ` João Távora [this message]
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
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=87pmactjy0.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=61478@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=felician.nemeth@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 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).