all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Javier Olaechea <pirata@gmail.com>
Cc: 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, 1 Feb 2024 23:42:16 -0800	[thread overview]
Message-ID: <CADwFkmm3R6hE+4hbze=Fm8sGiVVaph-4PpG6QKDR7jXUUJcG5g@mail.gmail.com> (raw)
In-Reply-To: <CAFVS=zAZrtAmODm9Rw21Dhw3W0wPGLQbHz3vtXde-h2LLma-jw@mail.gmail.com> (Javier Olaechea's message of "Sat, 14 Oct 2023 17:54:54 -0500")

Javier Olaechea <pirata@gmail.com> writes:

>> Great, then I'd say we should first apply your patch.
>
> I've also checked that it fixes the issue with ocamllsp. I agree that we should apply the change
> as it fixes the issue that Aaron is facing. I can work on the jsonrpc regardless and I will take into
> consideration the issues that you've mentioned

Javier, did you make any progress here?

Thanks.





  reply	other threads:[~2024-02-02  7:42 UTC|newest]

Thread overview: 14+ 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                       ` Stefan Kangas [this message]
2024-02-04  4:15                         ` bug#66144: 29.1; eglot-shutdown request params violate JSONRPC spec Javier Olaechea

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='CADwFkmm3R6hE+4hbze=Fm8sGiVVaph-4PpG6QKDR7jXUUJcG5g@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=66144@debbugs.gnu.org \
    --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.