[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: project.el semantics

From: Dmitry Gutov
Subject: Re: project.el semantics
Date: Sun, 8 Nov 2015 03:47:37 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Thunderbird/42.0

Hi Stephen,

On 09/18/2015 07:08 PM, Stephen Leake wrote:

That means project-search-path should be clearly defined to be either
purely recursive or not, so client code and project backends know
whether to weed out duplicates or not.

It also means the distinction between project-search-path and
project-roots must be more clearly defined.

Please see the commit 9776972 inside the branch project-next. I intend to merge it into master in a day or two.

Sorry to stir things around with the rename, but I think it's justified.

If there are use cases where different search paths are desired for
different purposes (such as "source" vs "documentation" above), the
the project API must provide a clear mechanism to distinguish those
cases, so the appropriate search path can be returned.

Also see the FIXME commentary above project-library-roots-function; it's waiting for the public opinion. Though it's not really about source vs documentation as much as about different kinds of sources.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]