Re: progmodes/project.el and search paths

[Dmitry Gutov]

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

> Since we are discussing core Emacs functionality, you should be clearer
> about this. There is a big difference between:

I doesn't seem particularly useful, and I don't want to work on it. But 
there's no reason to assume that I'm going to veto it (do I even have a 
veto power?), if someone's going to implement it in a clean way.

> Personally, I use 'make' much more than I use cross reference tools, so
> yes, build is more useful.

You can still run 'make' in the console, but cross-referencing needs an 
editor to function adequately.

> - 'compile' tries to provide tab completion on Makefile targets; it
> doesn't do it well (it misses targets in #include <makefile>).
> Presumably EDE can do better, so project.el should provide
> project-build-targets, so compile can use that to provide the completion
> list. That would then automatically work for ant, gradle, etc projects
> as those are added to EDE or another project implementation.

If project-build-targets just returns a list of strings, that would be 
insufficient to run the build. So we need a more informative structure.

name, description, full command to run. Maybe also cram running build 
targets in different environments in there somehow.

> - 'compile' also tries to guess the build command; it could use
> project-build-command.

Maybe all required info will be in project-build-targets. Or we'll just 
have project-default-target, which will return a simple string.