unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Ergus <spacibba@aol.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: projects.el and nested projects
Date: Sat, 11 Mar 2023 00:29:17 +0200	[thread overview]
Message-ID: <0364beca-5506-973c-f3eb-55a42be5c628@yandex.ru> (raw)
In-Reply-To: <20230310135748.rcfjzrzimnozj52y@Ergus>

Hi Ergus!

On 10/03/2023 15:57, Ergus wrote:

> I am working in a project with a nested setup (like an onion with 3 and
> 4 levels... VS way). I am wondering how could nested projects be
> supported in project.el. I know they were somehow in the past and now
> there is the project-external-roots, but I it does not look very used.
> 
> So the project root should be the top-most common directory?? Or is
> better to use the local/closer one in order to have better scope, and
> the add all the others as project-external-roots??
> 
> As the original project was for VS studio, I plan to create a sort of
> project.el backend for my use case, but I would like to know in advance
> a bit if it worth the effort.

I suppose it depends on what you want from that project, how you want it 
to behave.

If you just use the topmost root as the project root, what will you be 
missing?

Or if you make every nested project to be its own project, what will you 
be missing then? Will you want to do a global/multi-project search 
often? Or do a sort of parent-project-find-file sort of thing?

In the naive configuration, the latter could be done just by switching 
to the root of the topmost project. But if you're going to do it often, 
other solutions could help as well.



      reply	other threads:[~2023-03-10 22:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230310135748.rcfjzrzimnozj52y.ref@Ergus>
2023-03-10 13:57 ` projects.el and nested projects Ergus
2023-03-10 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=0364beca-5506-973c-f3eb-55a42be5c628@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=help-gnu-emacs@gnu.org \
    --cc=spacibba@aol.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.
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).