From: Dmitry Gutov <dmitry@gutov.dev>
To: Jim Porter <jporterbugs@gmail.com>,
Eric Gillespie <epg@pretzelnet.org>,
73736@debbugs.gnu.org
Subject: bug#73736: 31.0.50; project and therefore eglot don't work without git
Date: Sat, 12 Oct 2024 01:29:29 +0300 [thread overview]
Message-ID: <648dd5a0-e083-4046-b624-f8114791bd6e@gutov.dev> (raw)
In-Reply-To: <f4b1a71c-beb0-ef2c-a553-d4f48686cf13@gmail.com>
On 12/10/2024 00:49, Jim Porter wrote:
>> 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?
>
> I'm fine with recognizing ".project" by default, since it seems we'd
> just be adopting an already-existing practice. In addition to the cases
> already discussed, it seems that the Eclipse and STM32 IDEs also use a
> ".project" file at the project root for various things.
That's good to know.
> To turn it around though, are there cases we know of where we *wouldn't*
> want ".project" to mark a project root? Maybe if an Eclipse IDE project
> were in a Git subdir? (In that case, maybe ".project" should only be
> checked for as a fallback if we couldn't determine the project using a
> "real" VC file.)
That would require a new variable because
project-vc-extra-root-markers's original goal was to allow sub-projects
inside a VC repo (or projects outside of any repos).
At this point I'd rather recommend users who prefer a different behavior
to customize this var to a different value, removing .project from it.
prev parent reply other threads:[~2024-10-11 22:29 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
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 [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
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=648dd5a0-e083-4046-b624-f8114791bd6e@gutov.dev \
--to=dmitry@gutov.dev \
--cc=73736@debbugs.gnu.org \
--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 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).