From: Joost Kremers <joostkremers@fastmail.fm>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: Jim Porter <jporterbugs@gmail.com>,
73736@debbugs.gnu.org, Eric Gillespie <epg@pretzelnet.org>
Subject: bug#73736: 31.0.50; project and therefore eglot don't work without git
Date: Fri, 11 Oct 2024 10:53:24 +0200 [thread overview]
Message-ID: <86bjzrc96j.fsf@fastmail.fm> (raw)
In-Reply-To: <d7d8bfe4-7da3-46a1-b9ed-3da919218bf5@gutov.dev> (Dmitry Gutov's message of "Fri, 11 Oct 2024 00:59:54 +0300")
On Fri, Oct 11 2024, Dmitry Gutov wrote:
> On 10/10/2024 21:52, Jim Porter wrote:
>> On 10/10/2024 11:42 AM, Dmitry Gutov wrote:
>>> This isn't very plug-and-play, but you can customize project-vc-extra-
>>> root-markers to include any other files that distinguish the root of a
>>> project. For example, Cargo.toml.
>> I wonder, could major modes provide project.el with some default values
>> for that option? Then rust-mode could add Cargo.toml, python-mode could
>> add pyproject.toml, and so on.
>
> That's a natural question, but it would result in different results for
> "current project" for files in the same directory (which often enough use
> different major modes).
What about a single marker that works for any project? This is a
work-around that Projectile uses and I'm using it with project.el as well,
with:
```
(add-to-list 'project-vc-extra-root-markers ".project")
```
--
Joost Kremers
Life has its moments
next prev parent reply other threads:[~2024-10-11 8:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 16:44 bug#73736: 31.0.50; project and therefore eglot don't work without git Eric Gillespie
2024-10-10 18:42 ` Dmitry Gutov
2024-10-10 18:52 ` Jim Porter
2024-10-10 21:59 ` Dmitry Gutov
2024-10-11 8:53 ` Joost Kremers [this message]
2024-10-11 14:43 ` Dmitry Gutov
2024-10-11 17:40 ` Ship Mints
2024-10-11 21:19 ` Dmitry Gutov
2024-10-12 14:32 ` Ship Mints
2024-10-12 20:30 ` Dmitry Gutov
2024-10-13 16:10 ` Ship Mints
2024-10-11 21:49 ` Jim Porter
2024-10-11 22:29 ` Dmitry Gutov
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=86bjzrc96j.fsf@fastmail.fm \
--to=joostkremers@fastmail.fm \
--cc=73736@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=epg@pretzelnet.org \
--cc=jporterbugs@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.