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: Thu, 06 Aug 2015 03:01:03 -0500	[thread overview]
Message-ID: <867fp8c0cg.fsf@stephe-leake.org> (raw)
In-Reply-To: <55C1D79D.2020906@yandex.ru> (Dmitry Gutov's message of "Wed, 5 Aug 2015 12:30:05 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 08/05/2015 10:48 AM, Stephen Leake wrote:
>
>>> nor does it use grep-find-ignored-directories and
>>> grep-find-ignored-files.
>>
>> It should not use these directly; only via project-ignores.
>
> As long as we're reusing semantic-symref-find-references-by-name, we
> need some way to make it use the ignores. Probably not by making it
> aware of project.el.

Why not? that seems to fit perfectly with "provide project information
to other elisp programs"

>> I don't understand. Surely the concept "a project that is active in all
>> buffers" is independent of the actual project type?
>
> That's a trivial concept and piece of code. There's no reason to
> insist on reusing it.

There's a very good reason; there should be _one_ global variable that
stores the _one_ currently active project.

I don't care what backend provides the project; I just care that there
is exactly one.

>> If it's not in project.el, I'll have to add it to every new project type
>> I write; that will be a name conflict, at the very least.
>
> Not at all. The variable should be named according to each particular
> package it's in.

You are completely missing the point of this functionality.

-- 
-- Stephe



  reply	other threads:[~2015-08-06  8:01 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 [this message]
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
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=867fp8c0cg.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).