From: Stefan Kangas <stefankangas@gmail.com>
To: Javier Olaechea <pirata@gmail.com>
Cc: "Daniel Pettersson" <daniel@dpettersson.net>,
66144@debbugs.gnu.org, "Eli Zaretskii" <eliz@gnu.org>,
"João Távora" <joaotavora@gmail.com>
Subject: bug#66144: 29.1; eglot-shutdown request params violate JSONRPC spec
Date: Thu, 25 Jul 2024 00:06:28 -0700 [thread overview]
Message-ID: <CADwFkmkd38AWLrZRjYog+RCJr3hTr1Yfx=T=uxtd7KpRN2Hv0A@mail.gmail.com> (raw)
In-Reply-To: <CAFVS=zAjHrVRz_8b9W4Fw=6dznqq9XbiRLD-3-hr6Xsw8_bBEg@mail.gmail.com> (Javier Olaechea's message of "Sat, 3 Feb 2024 23:15:18 -0500")
Javier Olaechea <pirata@gmail.com> writes:
> I did sit down twice to read the jsonrpc.el code and understand what I need to do to make the
> change I hoped to. But unfortunately I can't even say I understood jsonrpc--async-request-1 well
> enough.Or even, if that is indeed the function we need to change so that we don't seed a params
> attribute when params is nil. It seems that we are passing the params down in multiple arms?
Daniel, can you help answer Javier's questions in this bug thread?
next prev parent reply other threads:[~2024-07-25 7:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 20:59 bug#66144: 29.1; eglot-shutdown request params violate JSONRPC spec Aaron Zeng
2023-10-08 3:42 ` bug#66144: 29.1; eglot-shutdown request params violate JSONRPC Javier Olaechea
2023-10-14 8:14 ` Eli Zaretskii
2023-10-14 8:59 ` João Távora
2023-10-14 16:59 ` Javier Olaechea
2023-10-14 17:13 ` João Távora
2023-10-14 17:19 ` Javier Olaechea
2023-10-14 18:02 ` João Távora
2023-10-14 18:33 ` João Távora
2023-10-14 20:14 ` Javier Olaechea
2023-10-14 20:32 ` João Távora
2023-10-14 22:54 ` Javier Olaechea
2024-02-02 7:42 ` bug#66144: 29.1; eglot-shutdown request params violate JSONRPC spec Stefan Kangas
2024-02-04 4:15 ` Javier Olaechea
2024-07-25 7:06 ` Stefan Kangas [this message]
2024-08-09 22:58 ` Daniel Pettersson
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='CADwFkmkd38AWLrZRjYog+RCJr3hTr1Yfx=T=uxtd7KpRN2Hv0A@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=66144@debbugs.gnu.org \
--cc=daniel@dpettersson.net \
--cc=eliz@gnu.org \
--cc=joaotavora@gmail.com \
--cc=pirata@gmail.com \
/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.