unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: running EDE from a file that is not under a project root dir
Date: Fri, 07 Aug 2015 09:15:02 -0500	[thread overview]
Message-ID: <864mkb89sp.fsf@stephe-leake.org> (raw)
In-Reply-To: <55C3D564.4060003@yandex.ru> (Dmitry Gutov's message of "Fri, 7 Aug 2015 00:45:08 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 08/06/2015 05:39 PM, Stephen Leake wrote:
>
>>> How so? As long as your project-find-functions element knows which
>>> variable to look up, you should be all set.
>>
>> How would it know that?
>>
>> Suppose I have a gpr project backend for AdaCore gprbuild projects, and
>> a gradle backend for Android gradle projects.
>
> I was assuming your project backends would share a codebase. But if
> they don't, they'll need to depend on a third package (which can be
> very small).

Right. That "third package" is project.el. What's wrong with that?

>> There are corresponding global variables; gpr-global-project,
>> gradle-global-project, each with a project-find function.
>
> The third package would contain: variable global-project-current,
> function global-project-visit, function global-project-try-it.

How is that different from declaring these in project.el?

>> I'm proposing to fix this by having one global variable with one
>> find-function.
>
> So I take it you're asking the above global-project to be moved to the
> core. 

Right.

> I'm hesitant, but it's better than what I originally understood
> your request to be (add the variable, and make it higher priority than
> project-find-functions).

It has the same priority as anything else in project-find-functions; if
the user wants to give it top priority, they put it first (or only).

> I wonder if the concept of the global project will be very popular.

It's in many current IDEs; Android Studio, Arduino, AdaCore GPS.

-- 
-- Stephe



  reply	other threads:[~2015-08-07 14:15 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 18:13 running EDE from a file that is not under a project root dir Stephen Leake
2015-08-04 23:18 ` Dmitry Gutov
2015-08-05  7:48   ` Stephen Leake
2015-08-05  9:30     ` Dmitry Gutov
2015-08-06  8:01       ` Stephen Leake
2015-08-06 10:34         ` Dmitry Gutov
2015-08-06 14:39           ` Stephen Leake
2015-08-06 21:45             ` Dmitry Gutov
2015-08-07 14:15               ` Stephen Leake [this message]
2015-08-05  1:57 ` Eric Ludlam
2015-08-05  6:43   ` Stephen Leake
2015-08-05  7:20     ` Stephen Leake
2015-08-05 15:09       ` Eli Zaretskii
2015-08-05 11:42     ` Eric Ludlam
2015-08-06  8:37       ` Stephen Leake
2015-08-06 10:55         ` David Engster
2015-08-06 14:55           ` Stephen Leake
2015-08-07 10:48             ` David Engster
2015-08-07 14:28               ` Stephen Leake
2015-08-07 14:53                 ` David Engster
2015-08-10 10:09             ` Steinar Bang
2015-08-06 11:44         ` Eric Ludlam
2015-08-06 15:03           ` Stephen Leake
2015-08-05 11:51     ` Eric Ludlam
2015-08-06  8:58       ` Stephen Leake
2015-08-08 15:26         ` Stephen Leake
2015-08-08 21:07           ` Eric Ludlam
2015-08-05  9:54   ` Dmitry Gutov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864mkb89sp.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).