all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Acid Bong <acidbong@tilde.club>
Cc: 74334@debbugs.gnu.org, 74334-done@debbugs.gnu.org
Subject: bug#74334: 29.4; Eglot ignores locally set configuration
Date: Wed, 13 Nov 2024 10:10:02 +0000	[thread overview]
Message-ID: <CALDnm51uGqEpB2uRtgTDJ+C-t3ULBm4mmG3y0aLyKURpvy=pdw@mail.gmail.com> (raw)
In-Reply-To: <fbbfda276583afcb6caaca8538f0bb94297b7959@tilde.club>

On Wed, Nov 13, 2024 at 9:45 AM Acid Bong <acidbong@tilde.club> wrote:

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

It's weird, but only because having this particular project very deep inside
the only dir that Emacs knows how to automatically recognize as a
project is weird.  Look into teaching project.el about "Cargo.toml" files,
it shouldn't be very hard.

You may or may not need "nested" projects, that's an orthogonal
issue.  If you're sure you do need nested or complicated project
setups,  look at [1])

João

[1]: https://github.com/joaotavora/eglot/discussions/1337#discussioncomment-8853117





      reply	other threads:[~2024-11-13 10:10 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 ` bug#74330: " 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 [this message]

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='CALDnm51uGqEpB2uRtgTDJ+C-t3ULBm4mmG3y0aLyKURpvy=pdw@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=74334-done@debbugs.gnu.org \
    --cc=74334@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.