Re: Subprojects in project.el

["João Távora" <joaotavora@gmail.com>]

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 26/11/22 02:00, João Távora wrote:

> We aren't even close to top efficiency WRT file operations now. And
> your idea is also based on hand-crafting project-find-functions to
> only contain the necessary items.

project-find-functions is part of project.el's API.  So it makes a lot
of sense to use, otherwise why would it be there?  We can provide some
pre-baked functions to put there, or already put there for users.  The
key point is that functions bail out early if they don't the adequate
context.  One of them is the one I proposed earlier, which uses a local
project-subproject-prefixes variable.  Another would search for marker
files and consult a tramp-specific user variable for opt-out.

> As opposed to real-life scenario of Projectile just adding its
> function at the front.
>
>>> I don't entirely understand the algorithm you're proposing here, but
>>> it sounds vaguely like what I'm writing now, so you might like the
>>> result.
>> Where/when can I find this code?
>
> You and others can now find it here: https://debbugs.gnu.org/41572#186

That thread has a latest patch that allows marker files to designate
top-level projects: I'm not interested in using marker files
specifically, so I don't see the relevance.  I can't deduce from the
patch what you're trying to solve or if it solves my use case.

Again, I'm interested in being able to designate projects that may only
exist inside other projects, and having a the C-x p family of commands
to allow a choice of inner project or any of the associated
super-projects.

There are maybe multiple ways to go about this: I've suggested what I
think is a promising one.

João