Re: A project-files implementation for Git projects

[Dmitry Gutov]

Hi Tassilo,

This general approach has been on my list for a while, and I'm thankful 
for help.

But we should get the details right, and IMO that means no "differences 
in semantics", and it implies certain requirements on the new VC backend 
action which we'll need to consider.

On 11.09.2019 23:01, Tassilo Horn wrote:
> here is a working solution for a VC list-files function.  I've added
> implementations for Git, Hg, Bzr, and SVN plus a default implementation
> which probably does the right thing for all other handled VC backends.
> I guess Monotone also has the ability to quickly list all tracked files
> but I haven't been able to install it.

I don't think there's a point in delegating to backends where the 
performance will end up being worse. Though I see you added a faster 
implementation for SVN later.

> I also added a vc `project-files' implementation which uses the VC
> list-files feature for backends in a new list-valued defcustom
> `project-vc-project-files-backends'.

That implementation should both include untracked files (since it's what 
we'd generally expect from it given the current Project API semantics) 
and honor project-vc-ignores (which is something a user can set via 
dir-locals, and I personally found quite useful).

Ideally it also should allow future support for whitelisting entries 
(that override ignores returned by Git), though that's not there yet.

All this makes creating new VC action more difficult, but I think we can 
do that. Maybe not for all backends, but Git for sure, which will help 
95% of our audience.