From: Dmitry Gutov <dmitry@gutov.dev>
To: Joost Kremers <joostkremers@fastmail.fm>
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 17:43:26 +0300 [thread overview]
Message-ID: <2a794cde-d7bb-4620-9a75-e693e164be83@gutov.dev> (raw)
In-Reply-To: <86bjzrc96j.fsf@fastmail.fm>
On 11/10/2024 11:53, Joost Kremers wrote:
>> 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")
> ```
That's the recommended course of action if you don't have other
consistent indicators of project root, between your projects.
I'm not a fan of adding a file that has no other purposes, but if people
find this useful, no problem. For personal projects it certainly
shouldn't hurt.
Eric, Jim, how would you like this resolution?
next prev parent reply other threads:[~2024-10-11 14:43 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
2024-10-11 14:43 ` Dmitry Gutov [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2a794cde-d7bb-4620-9a75-e693e164be83@gutov.dev \
--to=dmitry@gutov.dev \
--cc=73736@debbugs.gnu.org \
--cc=epg@pretzelnet.org \
--cc=joostkremers@fastmail.fm \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).