From: Dmitry Gutov <dgutov@yandex.ru>
To: "João Távora" <joaotavora@gmail.com>
Cc: Stephen Leake <stephen_leake@stephe-leake.org>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: cl-defgeneric vs random funcall in project.el
Date: Mon, 10 Aug 2015 22:37:00 +0300 [thread overview]
Message-ID: <55C8FD5C.5040602@yandex.ru> (raw)
In-Reply-To: <CALDnm51Tsnmy+LCo+b8+q62icCCoQ0gVxgjfWk8t4+A5q-21JQ@mail.gmail.com>
On 08/10/2015 10:21 PM, João Távora wrote:
> That's what I suspected, but Stephen said that you don't like it. I mistakenly
> took that as a suggestion that you wouldn't add the functionality to support
> it.
There's no way I even could do that: grep-project would use the same
project- methods as xref-find-regexp does now.
>> Either someone will have to write another backend (or several) that target
>> different build systems, or the VC backend will have to be equipped with a
>> pluggable facility for reading project files.
>>
>> Some combination of the two will probably turn out to be optimal.
>
> I agree. But I think you misunderstood me, these particular 5% are the ones
> where you're "off-the-hook",
Well, you mentioned Makefile targets, and we don't do anything with
those, so far. There's no "default" project structure which you could
adapt your projects for, except for "a root directory with files in it",
and depending on the language, etc, we might have to several of those.
next prev parent reply other threads:[~2015-08-10 19:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 11:31 cl-defgeneric vs random funcall in project.el Stephen Leake
2015-07-28 15:09 ` Dmitry Gutov
2015-07-28 23:57 ` Stefan Monnier
2015-07-29 0:16 ` Dmitry Gutov
2015-07-30 21:26 ` Stefan Monnier
2015-07-29 1:00 ` Stephen Leake
2015-07-29 1:19 ` Dmitry Gutov
2015-07-29 14:24 ` Stephen Leake
2015-07-29 19:54 ` Dmitry Gutov
2015-07-30 7:04 ` Stephen Leake
2015-07-30 11:30 ` Dmitry Gutov
2015-07-30 15:29 ` Stephen Leake
2015-07-30 15:37 ` Stephen Leake
2015-07-30 16:10 ` Dmitry Gutov
2015-07-30 23:25 ` Stephen Leake
2015-07-30 17:16 ` Dmitry Gutov
2015-07-30 23:33 ` Stephen Leake
2015-07-31 0:37 ` Dmitry Gutov
2015-07-31 14:36 ` Stephen Leake
2015-07-31 22:52 ` Dmitry Gutov
2015-08-01 10:21 ` Stephen Leake
2015-08-01 12:09 ` Dmitry Gutov
2015-08-01 14:20 ` Stephen Leake
2015-08-01 16:49 ` Dmitry Gutov
2015-08-01 19:08 ` Stephen Leake
2015-08-04 19:59 ` João Távora
2015-08-04 20:56 ` Dmitry Gutov
2015-08-04 22:43 ` João Távora
2015-08-04 23:35 ` Dmitry Gutov
2015-08-10 1:09 ` Dmitry Gutov
2015-08-10 3:07 ` Stephen Leake
2015-08-10 8:45 ` João Távora
2015-08-10 16:50 ` Stephen Leake
2015-08-10 19:38 ` João Távora
2015-08-10 18:07 ` Dmitry Gutov
2015-08-10 19:21 ` João Távora
2015-08-10 19:37 ` Dmitry Gutov [this message]
2015-08-10 19:47 ` João Távora
2015-08-10 19:55 ` Dmitry Gutov
2015-08-10 18:02 ` Dmitry Gutov
2015-08-07 15:02 ` Stefan Monnier
2015-08-07 15:32 ` Dmitry Gutov
2015-08-07 17:36 ` Stefan Monnier
2015-08-05 7:02 ` Stephen Leake
2015-07-30 21:31 ` Stefan Monnier
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=55C8FD5C.5040602@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=stephen_leake@stephe-leake.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).