From: "João Távora" <joaotavora@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Misha Zharov <mishazharov1@gmail.com>,
Felician Nemeth <felician.nemeth@gmail.com>,
63433@debbugs.gnu.org
Subject: bug#63433: Eglot "eglot--apply-workspace-edit > documentChanges > create" fails
Date: Thu, 7 Sep 2023 11:39:03 +0100 [thread overview]
Message-ID: <CALDnm50EupJHetWOFthVho6OqWHenjQu6=BZSmuNWu7nFRSCjw@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmncBAZMMumXU4yqCU2fJqJScmCRLU9VWiLWX8dsq1t8og@mail.gmail.com>
On Thu, Sep 7, 2023 at 10:59 AM Stefan Kangas <stefankangas@gmail.com> wrote:
>
> Felician Nemeth <felician.nemeth@gmail.com> writes:
>
> > In its initializationOptions, Eglot do not state that it supports any
> > resourceOperations. So the server made a mistake when it sent a
> > "create" kind.
> >
> > Sure, Eglot could handle better the server's mistake or support this
> > feature, but this is primarily a server bug in my opinion.
> >
> > Background:
> > https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspaceEditClientCapabilities
>
> João, any comments here?
Thanks for pinging.
But no, no further comments, I think Felicián's description is
very accurate.
But I would like to see Eglot support this of course.
João
next prev parent reply other threads:[~2023-09-07 10:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 4:49 bug#63433: Eglot "eglot--apply-workspace-edit > documentChanges > create" fails Misha Zharov
2023-05-11 6:35 ` Felician Nemeth
2023-05-11 7:09 ` Misha Zharov
2023-05-12 21:50 ` Richard Stallman
2023-05-12 22:35 ` Gregory Heytings
2023-05-15 22:13 ` Richard Stallman
2023-09-07 9:59 ` Stefan Kangas
2023-09-07 10:39 ` João Távora [this message]
2023-09-07 10:52 ` Felician Nemeth
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='CALDnm50EupJHetWOFthVho6OqWHenjQu6=BZSmuNWu7nFRSCjw@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=63433@debbugs.gnu.org \
--cc=felician.nemeth@gmail.com \
--cc=mishazharov1@gmail.com \
--cc=stefankangas@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.