all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Javier Olaechea <pirata@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 66144@debbugs.gnu.org
Subject: bug#66144: 29.1; eglot-shutdown request params violate JSONRPC
Date: Sat, 14 Oct 2023 12:19:04 -0500	[thread overview]
Message-ID: <CAFVS=zD-ArYktOQNpmb33riOf4TBqqXwu+GydE9wNJ6d4oh+rg@mail.gmail.com> (raw)
In-Reply-To: <CALDnm527O-uD6=8BCaww+Tbk9FHjHa8iZt2hPujx3373P5bEVQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 337 bytes --]

> If you can find some Eglot use case that is actually hurt by this, we can
reopen.

The OP has an Eglot use case that is hurt by this, they cannot shutdown the
ocamllsp server. Because when they call M-x eglot-shutdown, eglot sends an
invalid request. The server dies instead of returning a response and then
eglot restarts the server.

[-- Attachment #2: Type: text/html, Size: 426 bytes --]

  reply	other threads:[~2023-10-14 17:19 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 [this message]
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

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='CAFVS=zD-ArYktOQNpmb33riOf4TBqqXwu+GydE9wNJ6d4oh+rg@mail.gmail.com' \
    --to=pirata@gmail.com \
    --cc=66144@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=joaotavora@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.