all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Acid Bong via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 74334@debbugs.gnu.org
Cc: joaotavora@gmail.com
Subject: bug#74334: 29.4; Eglot ignores locally set configuration
Date: Tue, 12 Nov 2024 22:49:18 +0200	[thread overview]
Message-ID: <507CD52F-4D8E-4A62-81D6-B32723762507@tilde.club> (raw)

Can be observed on both builtin (1.12.29) and the newest Eglot (1.17). I'm starting Eglot manually, i have no hooks for Rust.

My repo structure:
/
...
|_pkgs/rsblocks/
  |_.dir-locals.el
  |_Cargo.toml
  ...

Since my Rust project isn't in the root of the repo, I need to specify its location for rust-analyzer. Using .dir-locals.el with this content:
```lisp
((nil
  . ((eglot-workspace-configuration
      . (:rust-analyzer (:linkedProjects ["pkgs/rsblocks/Cargo.toml"]))))))
;; thank god it supports relative paths
```
does nothing: I see the variable value is set properly with `C-h v`, but Eglot doesn't seem to recognize it (`eglot-show-workspace-configuration` shows "null").

However, only when I set it globally, Eglot can apply the config to the language server.

Expected behaviour: like described in the manual, Eglot should recognize local values. 

Possibly related report: https://github.com/joaotavora/eglot/issues/355 (unresolved)





             reply	other threads:[~2024-11-12 20:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 20:49 Acid Bong via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-11-12 21:34 ` bug#74330: 29.4; Eglot ignores locally set configuration João Távora
2024-11-13  8:03 ` bug#74334: " Acid Bong via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-13  8:39   ` João Távora
2024-11-13  9:45     ` Acid Bong via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-13 10:10       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=507CD52F-4D8E-4A62-81D6-B32723762507@tilde.club \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74334@debbugs.gnu.org \
    --cc=acidbong@tilde.club \
    --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 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.