From: "João Távora" <joaotavora@gmail.com>
To: Rajeev N <contact@sivalik.com>
Cc: 67150@debbugs.gnu.org
Subject: bug#67150: eglot with typescript language server >= 4.1.0
Date: Mon, 13 Nov 2023 16:49:32 +0000 [thread overview]
Message-ID: <CALDnm50iXH626voYzA7f1XdAMU4BTfmTPkyZJ3Nxk4QupTxZuw@mail.gmail.com> (raw)
In-Reply-To: <87msvh4nbw.fsf@hm.sivalik.com>
On Mon, Nov 13, 2023 at 4:42 PM Rajeev N <contact@sivalik.com> wrote:
>
> I am running the latest stable branch of emacs with the latest eglot from stable.
I'm sorry I don't know what "latest eglot from stable" is.
M-x emacs-version and the contents of the Version: header in the eglot.el
file are what's needed usually.
> The following fixed the issue for me.
>
> (add-to-list 'eglot-server-programs
> `(((js-mode :language-id "javascript")
> (js-ts-mode :language-id "javascript")
> (tsx-ts-mode :language-id "typescriptreact")
> typescript-ts-mode typescript-mode)
> .
> ("typescript-language-server" "--stdio")))
Oh, so "tsx" is not a valid language ID? For this particular
server, this particular server version, or universally?
How the heck are clients supposed to know that?
IOW where did you glean this information about language ids from?
Anyway, I think your modification makes sense regardless.
João
next prev parent reply other threads:[~2023-11-13 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 11:29 bug#67150: eglot with typescript language server >= 4.1.0 Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-13 16:37 ` João Távora
2023-11-13 16:42 ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-13 16:49 ` João Távora [this message]
2023-11-13 16:57 ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-14 0:12 ` João Távora
2023-11-14 12:07 ` Eli Zaretskii
2023-11-14 12:19 ` João Távora
2023-11-14 14:28 ` Eli Zaretskii
2023-11-15 9:51 ` Simon Pugnet
2023-11-15 10:18 ` João Távora
2023-11-15 10:27 ` Simon Pugnet
2023-11-15 10:29 ` 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=CALDnm50iXH626voYzA7f1XdAMU4BTfmTPkyZJ3Nxk4QupTxZuw@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=67150@debbugs.gnu.org \
--cc=contact@sivalik.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).