Re: master 370b216f086: New variable 'project-files-relative-names'

[Eli Zaretskii <eliz@gnu.org>]

> Date: Sun, 5 May 2024 18:46:30 +0300
> Cc: michael.albinus@gmx.de, emacs-devel@gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
> 
> On 05/05/2024 17:19, Eli Zaretskii wrote:
> > After some debugging, the reason seems to be the use of that
> > ":(exclude,glob,top)%s" thingie in project--vc-list-files.  Which
> > version of Git introduced it?
> 
> I don't know the exact version, but git pathspecs are mentioned in this 
> 2014 SO question and in this 2015 article:
> 
> https://stackoverflow.com/questions/27711924/whats-a-pathspec-in-the-git-command
> https://kgrz.io/git-intro-to-pathspec.html
> 
> That seems old enough to me?
> 
> And the use of this feature was added to project.el in 2020, FWIW.

Maybe it's some other problem with it, because these pathspecs are
documented in my Git's man pages, but the commands I tried came up
with an empty list on my system, but with a non-empty list on another
one, where a newer Git is installed.  Could you perhaps show an
example of such a command line that I could try here?

Regardless, top of the backtrace from the failure looks like this:

  Test project-vc-supports-project-in-different-dir backtrace:
    string-match("\0" nil 0)
    split-string(nil "\0" t)
    project--vc-list-files("d:/gnu/git/emacs/trunk/test/lisp/progmodes/p

IOW, it tries to split-string nil.