From: Felician Nemeth <felician.nemeth@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: 62198@debbugs.gnu.org, Alan Donovan <adonovan@google.com>
Subject: bug#62198: eglot feature request: set Initialize.ClientInfo.{Name, Version}
Date: Thu, 29 Jun 2023 17:46:37 +0200 [thread overview]
Message-ID: <87cz1es23m.fsf@betli.tmit.bme.hu> (raw)
In-Reply-To: <CALDnm52LdQwpubtSvDoASdSwRaeoV_+YwMhTWSUEvNro7Yz3zw@mail.gmail.com> ("João Távora"'s message of "Wed, 28 Jun 2023 22:02:40 +0100")
João Távora <joaotavora@gmail.com> writes:
> On Wed, Jun 28, 2023 at 9:41 PM Alan Donovan <adonovan@google.com> wrote:
>
>> > >Hi João,
>> > > would you mind making eglot populate the clientInfo.{name,version}
>> > > fields of the Initialize request parameters? All that's necessary is
>> > > the one-line change below, though I'm sure you know a cleaner way to
>> > >express the JSON literal and the version constant.
>> > No I wouldn't mind.
>> Great! I found that this expression works for the version, assuming
>> eglot is actually installed:
>>
>> (package-desc-version (cadr (assoc 'eglot package-alist)))
>
> That's the thing. Sometimes it is installed in that variable, sometimes
> it's a builtin described in some other variable. There is, I think,
> a library for this.
>
> I've found the bug thread: bug#62198.
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62198
>
> Taking the liberty of CCing there. Felicián was also looking for this.
If Eglot is installed, then it is byte-compiled as well. The earlier
patch in this bug report made sure that the helper library ('lisp-mnt)
was required only at compile time. However, the patch worked even if
Eglot was not installed with package.el (but Eglot still needed to be
byte-compiled).
On the other hand, if package-desc-version is acceptable as opposed to
that earlier patch, then it is probably better than not sending a
version number in clientInfo.
next prev parent reply other threads:[~2023-06-29 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPVWWDWmV3A1GhzvHFQhu2dz171ghgdwBRrtZbzWJP1ojiiO4w@mail.gmail.com>
[not found] ` <CALDnm52Jo8kQJtmLgDXHHdZWJ=OES4a2GGGU-U1VaObdN+fEBg@mail.gmail.com>
[not found] ` <CAPVWWDWCTvjzG3CLffnaf_xgn4R-Y8=j9y3to0yCEhoAt0gPMA@mail.gmail.com>
2023-06-28 21:02 ` bug#62198: eglot feature request: set Initialize.ClientInfo.{Name, Version} João Távora
2023-06-29 15:46 ` Felician Nemeth [this message]
2023-06-29 16:02 ` João Távora
2023-07-15 10:18 ` Felician Nemeth
2023-08-03 7:39 ` Eli Zaretskii
2023-08-03 10:15 ` João Távora
2023-08-03 10:20 ` Eli Zaretskii
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=87cz1es23m.fsf@betli.tmit.bme.hu \
--to=felician.nemeth@gmail.com \
--cc=62198@debbugs.gnu.org \
--cc=adonovan@google.com \
--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 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).