unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Benjamin Orthen <benjamin@orthen.net>, 60198@debbugs.gnu.org
Subject: bug#60198: 30.0.50; Eglot: Spelling error for vscode-json-languageserver
Date: Mon, 19 Dec 2022 14:19:08 +0000	[thread overview]
Message-ID: <CALDnm52-nXMB6xe-h2yeaRshjnv5bo9rnc0a+GExxaBDDqhEiQ@mail.gmail.com> (raw)
In-Reply-To: <83ili7eere.fsf@gnu.org>

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

That might be, Eli.  When people submit changes to the Eglot
eglot-server-programs, I rarely double-check to see if they actually
work.  As Brian points out, it does seem to work in some installations
of this language server.

Just as a data point, I myself almost always start my servers with
C-u M-x eglot and then proceed to find the right server using Emacs's
completion system. Even if the invocation is complicated, it will last
me through the session and  be available in my next session with
C-u M-x eglot M-p RET (because I use savehist-mode).

João

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

      reply	other threads:[~2022-12-19 14:19 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
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 [this message]

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=CALDnm52-nXMB6xe-h2yeaRshjnv5bo9rnc0a+GExxaBDDqhEiQ@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=60198@debbugs.gnu.org \
    --cc=benjamin@orthen.net \
    --cc=eliz@gnu.org \
    /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).