From: Dmitry Gutov <dgutov@yandex.ru>
To: Eric Ludlam <ericludlam@gmail.com>,
Emacs Development <emacs-devel@gnu.org>
Subject: Re: progmodes/project.el and search paths
Date: Tue, 11 Aug 2015 23:01:39 +0300 [thread overview]
Message-ID: <55CA54A3.1030104@yandex.ru> (raw)
In-Reply-To: <55C166EF.9060909@gmail.com>
Hi Eric,
Sorry for the late reply. I wasn't really sure what kind of response is
expected.
In short, I like your vision as a whole, but whether each particular
element of it can apply to project.el, should be investigated separately.
On some of them:
* I wonder what's the main use of having hierarchical projects vs.
simply tracking several currently open projects (or project roots). And
how the consumers of the API would take advantage of that distinction.
* Project services seem to be the proper way to handle optional traits
of significant size that some projects have, and others don't.
* "Project Loading safety" are probably out of scope. I'd expect the
majority of implementations to be based around loading a project build
(or settings) file of pre-existing format. The popular IDEs don't ask
the user whether they want to load the project file. On the other hand,
some project types might need to be enabled/visited explicitly.
* WRT "Detection ordering", the current project-find-functions structure
might be enough. Any Makefile project implementation will most likely go
before the VC project anyway (unless the respective add-hook form is
told to APPEND, for some reason). And it's hard for us to expect for
third-party implementations to be able to declare priorities between
themselves.
* "Update meta-data" might be handled by each respective implementation,
in conjunction with auto-revert-mode.
* "Project browsing" shouldn't need much more than project.el exposes
already.
* "Project Local Variables" look very similar to project metadata.
* The "'include path' concept" looks very similar to
project-search-path. This might be the main purpose for the
project-search-path entries that lie within project-roots.
* WRT cscope, etc, integration, I think the main unsolved problem we
currently have is that they aren't re-run automatically. Nor do we have
a command that would do that for the user on demand.
* "Load a project" seems incompatible with the project-find-functions
approach. Which is unfortunate.
* "navigating between code and doc", as stated, doesn't seem
particularly useful: if you're reading the source code of a function,
the docstring is usually right above. Jumping from the doc to the source
is better, but this is closer to the domain of xref.
* "Language specificity" might be useful, but in practical terms it
sounds like adding an optional (?) "language" argument to
project-search-path and any similar method that we add later. Which
complicates implementations. Or just have an Emacs-global repository of
file name patterns corresponding to languages? Not sure.
* "commands specific to project implementations" could also be added by
the minor modes supplied by the implementations' packages.
On 08/05/2015 04:29 AM, Eric Ludlam wrote:
> Emacs has a lot of tools that could use a project service, and sometimes
> all the tool needs is a small push of convenience, and not full project
> management system. A generic project system will make it easy to add
> small conveniences in lots of places you may not expect because tool
> authors will feel safe using it.
That's the idea, yes.
> The attached is my experience of things I either needed in EDE's base
> classes to implement a project, or that some tool needed, and what I
> learned along the way. You might think it is too EDE specific,
I wouldn't say the majority of items in the list are EDE specific.
> I consider this file incomplete, but I hope it proves useful as a
> starting point. I'd be happy to periodically update it for a little
> while if it is useful.
Were we using a nice issue tracker, I'd have asked to create a tracking
issue (or would've created one myself), but in the present situation, I
guess you'll have to resend it with updates.
But in any case, I'd say technical proposals on specific features, as
well as patches, would provide more value here, rather than maintaining
a high-level overview of things we might get around to someday.
next prev parent reply other threads:[~2015-08-11 20:01 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 13:52 progmodes/project.el and search paths Eric Ludlam
2015-08-02 17:17 ` Dmitry Gutov
2015-08-03 1:19 ` Eric Ludlam
2015-08-03 16:16 ` Stephen Leake
2015-08-03 22:56 ` Dmitry Gutov
2015-08-08 13:07 ` Nix
2015-08-09 5:18 ` Stephen Leake
2015-08-09 12:17 ` David Engster
2015-08-09 15:55 ` Stephen Leake
2015-08-10 11:29 ` David Engster
2015-08-10 16:43 ` Stephen Leake
2015-08-12 10:10 ` David Engster
2015-08-12 13:49 ` Stephen Leake
2015-08-12 15:36 ` David Engster
2015-08-13 11:53 ` Nix
2015-08-13 12:05 ` Dmitry Gutov
2015-08-14 11:52 ` Eric Ludlam
2015-08-14 22:30 ` Dmitry Gutov
2015-08-15 0:48 ` Eric Ludlam
2015-08-15 7:05 ` Eli Zaretskii
2015-08-10 17:12 ` Nix
2015-08-03 22:47 ` Dmitry Gutov
2015-08-04 11:52 ` Eric Ludlam
2015-08-04 16:09 ` Dmitry Gutov
2015-08-03 13:49 ` David Engster
2015-08-03 14:09 ` Dmitry Gutov
2015-08-03 14:27 ` David Engster
2015-08-03 15:13 ` Dmitry Gutov
2015-08-03 21:35 ` David Engster
2015-08-03 23:21 ` Dmitry Gutov
2015-08-04 8:15 ` David Engster
2015-08-04 13:43 ` Eli Zaretskii
2015-08-04 18:05 ` Dmitry Gutov
2015-08-04 18:16 ` Eli Zaretskii
2015-08-04 18:41 ` Dmitry Gutov
2015-08-04 19:23 ` Eli Zaretskii
2015-08-04 19:40 ` João Távora
2015-08-05 2:52 ` Eli Zaretskii
2015-08-04 20:15 ` Dmitry Gutov
2015-08-05 2:49 ` Eli Zaretskii
2015-08-05 6:18 ` Stephen Leake
2015-08-05 15:08 ` Eli Zaretskii
2015-08-05 15:36 ` Dmitry Gutov
2015-08-05 16:31 ` Eli Zaretskii
2015-08-05 16:45 ` David Engster
2015-08-05 22:17 ` Dmitry Gutov
2015-08-06 7:56 ` Stephen Leake
2015-08-06 7:54 ` Stephen Leake
2015-08-05 9:42 ` Dmitry Gutov
2015-08-05 15:23 ` Eli Zaretskii
2015-08-05 15:31 ` Dmitry Gutov
2015-08-05 16:16 ` Eli Zaretskii
2015-08-06 6:44 ` Dmitry Gutov
2015-08-06 7:43 ` Stephen Leake
2015-08-06 10:25 ` Dmitry Gutov
2015-08-06 14:27 ` Stephen Leake
2015-08-06 23:16 ` Dmitry Gutov
2015-08-07 14:10 ` Stephen Leake
2015-08-07 14:44 ` Dmitry Gutov
2015-08-03 16:35 ` Stephen Leake
2015-08-03 16:45 ` Eli Zaretskii
2015-08-03 21:07 ` Stephen Leake
2015-08-03 21:33 ` David Engster
2015-08-04 2:35 ` Eli Zaretskii
2015-08-03 15:09 ` Eli Zaretskii
2015-08-03 15:16 ` Dmitry Gutov
2015-08-03 15:29 ` Eli Zaretskii
2015-08-03 19:01 ` Dmitry Gutov
2015-08-03 19:19 ` Eli Zaretskii
2015-08-03 21:05 ` Dmitry Gutov
2015-08-04 11:48 ` Eric Ludlam
2015-08-04 16:20 ` Dmitry Gutov
2015-08-03 16:25 ` Stephen Leake
2015-08-03 21:33 ` Stefan Monnier
2015-08-03 22:15 ` David Engster
2015-08-03 22:50 ` Dmitry Gutov
2015-08-04 7:13 ` Stefan Monnier
2015-08-04 8:13 ` David Engster
2015-08-05 13:42 ` Stefan Monnier
2015-08-06 11:27 ` {Spam?} " Eric Ludlam
2015-08-06 23:10 ` Stefan Monnier
2015-08-07 11:18 ` Eric Ludlam
2015-08-07 11:43 ` David Engster
2015-08-07 12:17 ` Dmitry Gutov
2015-08-07 12:40 ` David Engster
2015-08-07 12:54 ` Dmitry Gutov
2015-08-07 12:08 ` Alexis
2015-08-04 9:40 ` Stephen Leake
2015-08-04 17:43 ` Dmitry Gutov
2015-08-04 19:49 ` Stephen Leake
2015-08-04 20:03 ` Dmitry Gutov
2015-08-05 6:02 ` Stephen Leake
2015-08-05 9:59 ` Dmitry Gutov
2015-08-06 7:25 ` Stephen Leake
2015-08-07 14:21 ` Dmitry Gutov
2015-08-05 1:29 ` Eric Ludlam
2015-08-11 20:01 ` Dmitry Gutov [this message]
2015-08-12 0:49 ` Eric Ludlam
2015-08-12 7:25 ` project terminology Stephen Leake
2015-08-12 9:28 ` progmodes/project.el and search paths Dmitry Gutov
2015-12-29 2:00 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55CA54A3.1030104@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=ericludlam@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.