Re: master 1e3b0f2: Improve doc strings of project.el

[Theodor Thornhill]

"Eli Zaretskii" <eliz@gnu.org> writes:

> Why does it matter that project-find-regexp uses *XREF*?  the question
> is why would you need to switch to it when it is not displayed in any
> window?
I don't always use a very big computer screen, so sometimes I don't
split the screen.
>
>> I believe I read you wouldn't want it. I guess many others will have
>> many different opinions in this matter.
>
> When I work with xref-related features, I keep the *XREF* buffer on
> display as long as I use it.  When I'm done using it, I don't care
> about it anymore.
Same here, though I have wanted to jump back to one. Not always, but
certainly not never.

> In any case, there's just one such buffer, so switching to it is easy.
Yeah, sure. I could use "switch-to-buffer" for that, but then I have to
context switch only a little. It isn't the end of the world at all, but
I'd like to have it there. (Though I didn't include it until Andrii
mentioned it)
>
>> In addition, when do we make that first desicion, really? Right now it
>> just sort of happens after you go "git init" in terminal. To me it
>> sounds like that new workflow adds some steps to what is right now a
>> quite seamless experience.
>
> That we mainly support projects that piggy-back VCS repositories
> doesn't mean that's the only kind of project that could be useful.
I definitively agree here.

> And even if the backend is Git, no one said that I want all of the
> files in the repository to be part of my project.  I may be working on
> a project that includes just a handful of files from a repository that
> has thousands of them.
True. I believe this is not yet supported fully by the api. For example,
a huge monorepo with .git only in root is a struggle.

Theo