From: "João Távora" <joaotavora@gmail.com>
To: Troy Brown <brownts@troybrown.dev>
Cc: Eli Zaretskii <eliz@gnu.org>,
monnier@iro.umontreal.ca, 73280@debbugs.gnu.org
Subject: bug#73280: 30.0.90; Eglot: eglot-workspace-configuration might not be found in .dir-locals.el
Date: Mon, 16 Sep 2024 20:07:57 +0100 [thread overview]
Message-ID: <CALDnm52bMP71BVcazV2AZ+PKQAoL3A_asvWzP3B9hmmQu+QQSg@mail.gmail.com> (raw)
In-Reply-To: <CABvCZ416iSqrm53LUNth3bLn42EXvKZCrhAvX_DM4=wLSV75og@mail.gmail.com>
On Mon, Sep 16, 2024 at 7:54 PM Troy Brown <brownts@troybrown.dev> wrote:
> That would be fine if this was isolated to only "ts" vs "non-ts"
> modes. Another example is "typescript-mode". In order to configure
> the server, you have to use "js-mode" in .dir-locals.el. Why?
> Because it's the first one in the list.
Well, typescript is a transpile-to-js language, doesn't strike me as
that odd.
Also have you read section 5.1.1 of the Eglot's user manual? You
can just use `nil` as the mode and `w-s-configuration` will
be set buffer-locally in all modes for buffers within that dir.
This is probably easier. Check it out.
next prev parent reply other threads:[~2024-09-16 19:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 19:54 bug#73280: 30.0.90; Eglot: eglot-workspace-configuration might not be found in .dir-locals.el Troy Brown
2024-09-16 11:38 ` Eli Zaretskii
2024-09-16 13:48 ` João Távora
2024-09-16 17:07 ` Troy Brown
2024-09-16 18:15 ` Eli Zaretskii
2024-09-16 18:39 ` João Távora
2024-09-16 18:43 ` Eli Zaretskii
2024-09-16 18:53 ` Troy Brown
2024-09-16 19:07 ` João Távora [this message]
2024-09-16 21:34 ` Troy Brown
2024-09-16 19:17 ` Eli Zaretskii
2024-09-16 21:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALDnm52bMP71BVcazV2AZ+PKQAoL3A_asvWzP3B9hmmQu+QQSg@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=73280@debbugs.gnu.org \
--cc=brownts@troybrown.dev \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.