From: Dmitry Gutov <dgutov@yandex.ru>
To: Felician Nemeth <felician.nemeth@gmail.com>, 41955@debbugs.gnu.org
Cc: Theodor Thornhill <theo@thornhill.no>
Subject: bug#41955: 28.0.50; Monorepos and project.el
Date: Tue, 23 Jun 2020 00:06:00 +0300 [thread overview]
Message-ID: <729a5f46-ddbd-4c50-50fc-c695865cc3e3@yandex.ru> (raw)
In-Reply-To: <87pn9rggui.fsf@betli.tmit.bme.hu>
On 22.06.2020 20:17, Felician Nemeth wrote:
> I'm not completely sure, because I haven't really used EDE (the Emacs
> Development Environment), but I think you can specify a project like
> that in EDE. And project.el supports EDE if I recall correctly. So
> maybe this complex "monorepo" use-case is already covered by existing
> features of Emacs.
Interesting thought.
The current EDE integration is pretty basic (only project-root,
basically), but it can be extended fairly quickly, if an EDE project
contains relevant data.
But that doesn't seem to be the case: it seems to me that EDE uses the
same "one directory tree" model for the contents of the project. And the
:include-path and :system-include-path keys we see in the definition
examples are about code analysis (where to find external type and
function definitions), and not about describing the main bulk of the
files belonging to the project.
next prev parent reply other threads:[~2020-06-22 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 20:42 bug#41955: 28.0.50; Monorepos and project.el Theodor Thornhill
2020-06-20 7:17 ` Eli Zaretskii
2020-06-20 7:48 ` Theodor Thornhill
2020-06-20 8:57 ` Eli Zaretskii
2020-06-21 1:25 ` Dmitry Gutov
2020-06-22 17:17 ` Felician Nemeth
2020-06-22 21:06 ` Dmitry Gutov [this message]
2020-06-20 23:29 ` Juri Linkov
2020-06-21 1:23 ` Dmitry Gutov
2020-06-21 1:48 ` 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=729a5f46-ddbd-4c50-50fc-c695865cc3e3@yandex.ru \
--to=dgutov@yandex.ru \
--cc=41955@debbugs.gnu.org \
--cc=felician.nemeth@gmail.com \
--cc=theo@thornhill.no \
/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).