From: Eric Ludlam <eric@siege-engine.com>
To: Stephen Leake <stephen_leake@stephe-leake.org>, emacs-devel@gnu.org
Subject: Re: running EDE from a file that is not under a project root dir
Date: Tue, 04 Aug 2015 21:57:07 -0400 [thread overview]
Message-ID: <55C16D73.6080801@siege-engine.com> (raw)
In-Reply-To: <861tfiexaz.fsf@stephe-leake.org>
On 08/04/2015 02:13 PM, Stephen Leake wrote:
> I often have "notes" files that are outside a project directory. For
> example, my Emacs notes are not in the emacs/master directory; it is
> controlled by git, and I don't want to commit my notes to that, nor
> clutter .gitignore.
>
> At the same time, I'd like to be able to invoke "search for symbol at
> point" from the notes text buffer; I have notes on functions/vars I'm
> using at the moment.
...
> My question is this; what is the minimum change I should make to EDE to
> support these use cases?
>
> I think I need three things:
>
> - add a "file patterns" element to the EDE project (or target?) data
> structure, and have semantic-symref-derive-find-filepatterns check that
> before the alists.
I'm not sure what matching file patterns has to do with core project
functionality. Your use case sounds like something that would want a
specialized tool, the same way there are tools that jump between 'doc'
and 'code'.
For example, if you keep notes in org mode (I assume everyone here uses
org mode these days) then perhaps what is needed is tooling that knows
how to keep TODO files in an org file tied to a project and the desired
language, and then the project would form the root of any symref call.
I suspect symref needs a tweak so that the major mode in question is
passed along far enough to get into the pattern matcher. Once that is
done, a tool that goes from your notes to src could call symref however
it is needed.
> - add an ede-global-project variable that I can set to my current
> project, to bypass the project root detection.
>
> I've proposed the same change to project.el; there, it can be used
> by one of the project-find functions.
I find the global project concept scary. I can't say how many times
I've edited Emacs code that was wasn't on my load path because I had
multiple checkouts of the same code. Mostly just too many times.
> - some way to set up the EDE project object for elisp, especially the
> file patterns.
I don't think you need to do anything project specific here. Symref
doesn't do anything with EDE past getting the root.
> The EDE info manual in Emacs master mentions ede-proj-elisp.el in
> section 8 Extending EDE, but I don't see that file in Emacs master
> git.
That is a piece of the large Make/Automake project system that builds
makefiles for you. Symref only uses EDE to identify a starting place
for the search, or a place to find tooling caches (like GTAGS). EDE is
then used by the semantic part that builds up the output buffer by
parsing tags which needs various include paths depending on language.
Eric
next prev parent reply other threads:[~2015-08-05 1:57 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
2015-08-05 1:57 ` Eric Ludlam [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55C16D73.6080801@siege-engine.com \
--to=eric@siege-engine.com \
--cc=emacs-devel@gnu.org \
--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 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.