From: Dmitry Gutov <dgutov@yandex.ru>
To: Ergus <spacibba@aol.com>, emacs-devel@gnu.org
Subject: Re: Should EDE use project.el [PATCH]
Date: Mon, 16 May 2022 18:50:59 +0300 [thread overview]
Message-ID: <c79278d2-0bdd-a9d4-0381-0b8147a28f50@yandex.ru> (raw)
In-Reply-To: <20220516150035.f5yryr6uby6msfqy@Ergus>
On 16.05.2022 18:00, Ergus wrote:
> Hi:
>
> I just attached an extremely simple (intested) attempt to make cedet use
> Project.el.. Maybe Dmitry or someone with more experience may complete
> this and extend it when possible?
Looks okay to me.
To give more detailed feedback, one might need more knowledge of CEDET,
I think
Do you use it? CEDET, I mean. If yes, this can be a beneficial direction
to go in. My observations say it's only falling out of favor, though.
>
> Best,
> Ergus
>
> On Mon, May 16, 2022 at 01:46:43PM +0200, Ergus wrote:
>> Hi:
>>
>> Recently working in the gtags-mode package I thought to add a backend
>> for ede/cedet... but I have found that most of the ede features overlap
>> or coincide with ones in project.el.
>>
>> So my question is: Isn't it easier to add a backend in locate.el to make
>> ede use project as one ede-locate-setup-options?
>>
>> I am not sure about how useful is ede or cedet these days as they seem
>> to be a bit unmaintained, but IMHO, if we don't want to remove them (for
>> some reason) but still keep project.el as the preferred way to go, then
>> maybe cedet should use the project.el functions by default.
>>
>> The basic implementation seems to need only:
>>
>> initialize-instance
>> ede-locate-ok-in-project
>> ede-locate-file-in-project-impl
>> ede-locate-create/update-root-database
>>
>> Implementing all these may be extremely simple but not sure if it worth
>> the effort.
>>
>> What do you suggest?
>>
>> Best,
>> Ergus
>>
next prev parent reply other threads:[~2022-05-16 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220516114643.5234do3n6zbyxv7r.ref@Ergus>
2022-05-16 11:46 ` Should EDE use project.el Ergus
2022-05-16 15:00 ` Should EDE use project.el [PATCH] Ergus
2022-05-16 15:50 ` Dmitry Gutov [this message]
2022-05-16 16:09 ` Ergus
2022-05-16 17:15 ` Eli Zaretskii
2022-05-16 19:40 ` andres.ramirez
2022-05-16 16:23 ` Ergus
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=c79278d2-0bdd-a9d4-0381-0b8147a28f50@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=spacibba@aol.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 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).