Subject: Re: bug#41572: 28.0.50; [PATCH] Support plain project marked with file .emacs-project

From: Eli Zaretskii <[email-masked]>
Date: Sat, 26 Nov 2022 09:47:53 +0200

> Cc: "Philip K." <[email-masked]>, Rudi Schlatte <[email-masked]>,
>  Augusto Stoffel <[email-masked]>, Zhu Zihao <[email-masked]>,
>  Theodor Thornhill <[email-masked]>,
>  Daniel Martín <[email-masked]>,
>  Eric Abrahamsen <[email-masked]>,
>  João Távora <[email-masked]>,
>  Manuel Uberti <[email-masked]>, Juri Linkov <[email-masked]>,
>  Rudolf Adamkovič <[email-masked]>
> Date: Sat, 26 Nov 2022 03:49:36 +0200
> From: Dmitry Gutov <[email-masked]>
> 
> Does this work for everybody?

Hard to say, because:

> +(defcustom project-vc-extra-root-markers nil
> +  "List of additional \"markers\" to signal project roots.
> +
> +A marker is either a base file name or a glob pattern for such.
> +
> +These will be used in addition to regular directory markers such
> +as .git, .hg, and so on, dependent on the value of
> +`vc-handled-backends'.

"These will be used" how?  This crucial information is sorely missing from
this description.  Likewise, how "markers" that are not files are used and
are useful?

>                         They are most useful when a VC project
> +has subdirectories inside it that need to be considered as
> +separate projects, but still use the parent's ignore rules and
> +general behaviors.

How are "markers" useful in this scenario?

> +It can also be used for projects outside of VC repositories.
> +Their behavior will still obey the relevant variables, such as
> +`project-vc-ignores' or `project-vc-name'."

And in this one?

IOW, please describe the main ideas of this approach instead of relying on
use immediately gleaning that from a patch with incomplete documentation.

TIA