From: Benjamin Orthen <benjamin@orthen.net>
To: Brian Leung <leungbk@posteo.net>
Cc: 60198@debbugs.gnu.org
Subject: bug#60198: 30.0.50; Eglot: Spelling error for vscode-json-languageserver
Date: Mon, 19 Dec 2022 15:17:07 +0100 [thread overview]
Message-ID: <06D08E3D-38D8-441C-AE67-01EACA0029A4@orthen.net> (raw)
In-Reply-To: <87359by375.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
Alright thanks, I wasn't aware of the extracted versions.
I still think vscode-json-languageserver should be included, as this is the "original" program and not everybody might know or use the extracted langservers you're quoting.
On December 19, 2022 1:42:54 PM GMT+01:00, Brian Leung <leungbk@posteo.net> wrote:
>Benjamin Orthen <benjamin@orthen.net> writes:
>
>> In lisp/progmodes/eglot.el:192,
>> "vscode-json-languageserver"
>> (https://www.npmjs.com/package/vscode-json-languageserver) is spelled as "vscode-json-language-server",
>> which causes eglot to fail to find the executable.
>
>It's not a spelling error;
>https://github.com/hrsh7th/vscode-langservers-extracted exposes an
>executable with that name. If you happen to use Nix, the
>nodePackages.vscode-langservers-extracted provides additional
>executables for HTML, CSS, and more.
>
>We could add vscode-json-languageserver as an additional executable to eglot-server-programs.
>
[-- Attachment #2: Type: text/html, Size: 1517 bytes --]
next prev parent reply other threads:[~2022-12-19 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 10:13 bug#60198: 30.0.50; Eglot: Spelling error for vscode-json-languageserver Benjamin Orthen
2022-12-19 12:42 ` Brian Leung
2022-12-19 13:00 ` Eli Zaretskii
2022-12-19 23:07 ` Brian Leung
2022-12-20 3:36 ` Eli Zaretskii
2022-12-20 10:21 ` Brian Leung
2022-12-19 14:17 ` Benjamin Orthen [this message]
2022-12-19 23:04 ` Brian Leung
2022-12-20 1:12 ` João Távora
2022-12-20 10:25 ` Brian Leung
2022-12-20 14:32 ` Eli Zaretskii
2023-09-05 23:51 ` Stefan Kangas
2022-12-19 12:53 ` Eli Zaretskii
2022-12-19 14:19 ` João Távora
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=06D08E3D-38D8-441C-AE67-01EACA0029A4@orthen.net \
--to=benjamin@orthen.net \
--cc=60198@debbugs.gnu.org \
--cc=leungbk@posteo.net \
/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).