Subject: Re: 29.4; Eglot ignores locally set configuration

From: "Acid Bong" <[email-masked]>
Date: Wed, 13 Nov 2024 09:45:37 +0000

> On Wed, Nov 13, 2024 at 8:03 AM Acid Bong <[email-masked]> wrote:
> 
> > 
> > Ight, Joao, you accidentally created a new report, but i'll answer your questions under the original one.
> > 
> 
> Bug in tracker, likely you weren't vetted yet. Reply all usually
> works and fetches the bug report. Who's Ight?
> 

It's short for "alright", sorry for confusing you.

> 
> > 
> > Speaking of `project-current`: I tried to follow the advices from
> >  https://github.com/joaotavora/eglot/discussions/687 and add "Cargo.toml"
> >  and "Cargo.lock" to `project-vc-extra-root-markers`, but `M-: (project-current)`
> >  still shows "~/.config/nixos". Looks like project.el can't recognize nested
> >  projects (both 0.9.8 and 0.11.0), but that's a whole different issue I don't care about.
> 
> You probably should care because .dir-locals needs to exist in the
> project root directory. Read the manual
>  https://joaotavora.github.io/eglot/#Project_002dspecific-configuration
> "The most common way to set eglot-workspace-configuration is using a
> .dir-locals.el file in the root of your project."
> 
> M-x eglot doesn't much care where inside a given project you start it. For
> all it knows you could started it visiting ight.rs in your nixis dir and it'd
> be the same.
> 

Woah, it actually works. Kinda weird that it requires .dir-locals.el to be in the
Git root, not in the Cargo root.

Thanks a lot