From: "João Távora" <joaotavora@gmail.com>
To: Acid Bong <acidbong@tilde.club>
Cc: 74330@debbugs.gnu.org
Subject: bug#74330: 29.4; Eglot ignores locally set configuration
Date: Tue, 12 Nov 2024 21:34:38 +0000 [thread overview]
Message-ID: <CALDnm501FKAD4nrtq1nYnyarvEJ3B5QUkWOVM60-en+6pYeWKQ@mail.gmail.com> (raw)
In-Reply-To: <507CD52F-4D8E-4A62-81D6-B32723762507@tilde.club>
On Tue, Nov 12, 2024 at 8:49 PM Acid Bong <acidbong@tilde.club> wrote:
> ```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").
What is the '...'preceding your excerpt of a structure?
Where are you executing C-h v? What file are you M-x eglot'int in?
Where are you running M-x eglot-show-worspace-configuration ?
What does M-: (project-current) RET show?
All these commands are highly dependent on context, so I think it's best if you
show a full recipe from Emacs -Q to clear these doubts. Only seeing part
of the repo structure isn't enough to really understand what's going on.
I really need to understand what you did (close to what keys you pressed)
until you got to the suprising effect. I have rust-analyzer (though I don't
have any suitable rust projects).
João
next prev parent reply other threads:[~2024-11-12 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 20:49 bug#74334: 29.4; Eglot ignores locally set configuration Acid Bong via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-12 21:34 ` João Távora [this message]
2024-11-13 8:03 ` 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=CALDnm501FKAD4nrtq1nYnyarvEJ3B5QUkWOVM60-en+6pYeWKQ@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=74330@debbugs.gnu.org \
--cc=acidbong@tilde.club \
/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.