unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Marcin Pajkowski" <marcin.pajkowski@gmail.com>,
	"João Távora" <joaotavora@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] Eglot: auto-import completion item
Date: Thu, 17 Nov 2022 11:50:19 +0200	[thread overview]
Message-ID: <83a64pewpw.fsf@gnu.org> (raw)
In-Reply-To: <CAPZ_WRHhnEfceY8GGNrs2sUqVFKsyZuKaixe39FkUe6zrBddTw@mail.gmail.com> (message from Marcin Pajkowski on Sat, 12 Nov 2022 14:23:52 +0100)

> From: Marcin Pajkowski <marcin.pajkowski@gmail.com>
> Date: Sat, 12 Nov 2022 14:23:52 +0100
> 
> * lisp/progmodes/eglot.el (eglot-client-capabilities): Advertise
> resolveSupport capabilities
> ---
>  lisp/progmodes/eglot.el | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/lisp/progmodes/eglot.el b/lisp/progmodes/eglot.el
> index 63ebbe6cab..953c0f45fc 100644
> --- a/lisp/progmodes/eglot.el
> +++ b/lisp/progmodes/eglot.el
> @@ -736,6 +736,7 @@ eglot-client-capabilities
>                                             t
>                                           :json-false)
>                                        :deprecatedSupport t
> +                                      :resolveSupport (:properties ["documentation" "details" "additionalTextEdits"])
>                                        :tagSupport (:valueSet [1]))
>                                      :contextSupport t)
>               :hover              (list :dynamicRegistration :json-false
> -- 
> 2.38.1

João, what about this one?  Should we install it?  What are
resolveSupport capabilities about?




  reply	other threads:[~2022-11-17  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-12 13:23 [PATCH] Eglot: auto-import completion item Marcin Pajkowski
2022-11-17  9:50 ` Eli Zaretskii [this message]
2022-11-17 10:41   ` João Távora
2022-11-20 20:52     ` Marcin Pajkowski
2022-11-21 13:56       ` João Távora
2022-11-22 20:26         ` Marcin Pajkowski

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=83a64pewpw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=marcin.pajkowski@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 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).