emacs-devel
[Top][All Lists]
Advanced

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

Re: progmodes/project.el and search paths


From: Dmitry Gutov
Subject: Re: progmodes/project.el and search paths
Date: Fri, 7 Aug 2015 17:21:28 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Thunderbird/40.0

On 08/06/2015 10:25 AM, Stephen Leake wrote:

I think we should have project-find-regexp (or project-rgrep) which
uses the xref interface. grep-project will be functionally redundant.

Since they are the same function, why is the name project-find-regexp
better than the name grep-project?

project-rgrep sounds just as good to me (M-x grep is flat).

Would grep-project, in your view, use the xref interface? If not, they're not the same either.

The latter will be _much_ easier to discover for the current grep user;
M-x gre<tab> will show it.

On the other hand, M-x project-<tab> won't. And the user won't be able to discover all core commands that work on the current project.

Both problems should be solved by making execute-extended-command use a new completion category that would perform laxer matching.

The purpose of project.el is to provide access to project information to
other elisp programs; it is _not_ to provide user level programs.

It's the purpose of the API. Nothing says we can't provide some commands that use the API together with it.

We could move them to a yet-another package is that's the consensus, but there is value in keeping them together.

Not every project command is going to have a "normal" counterpart.



reply via email to

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