unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ergus <spacibba@aol.com>
Cc: dgutov@yandex.ru, emacs-devel@gnu.org
Subject: Re: Should EDE use project.el [PATCH]
Date: Mon, 16 May 2022 20:15:17 +0300	[thread overview]
Message-ID: <83fsl9iel6.fsf@gnu.org> (raw)
In-Reply-To: <20220516160938.6i5hy65l5s5d7in3@Ergus> (message from Ergus on Mon, 16 May 2022 18:09:38 +0200)

> Date: Mon, 16 May 2022 18:09:38 +0200
> From: Ergus <spacibba@aol.com>
> Cc: emacs-devel@gnu.org
> 
> >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.
> >
> Actually I don't know how to use it properly yet. I just tried this
> because I tried something with gtags and I found that it has its own
> backend for global/gtags BUT un-optimized and tramp and similes fail (as
> expected).
> 
> The last commit in their git repo was in 2019 and it seems to be almost
> totally unmaintained (in a quick test I found some issues
> immediately)... which means I am not even sure if there is anyone still
> using it.
> 
> So my first recommendation would be to remove/deprecate it in favor of
> project.el

CEDET includes many features that project.el doesn't have (and AFAIU
is not intended to have any time soon, if at all).  Moreover, some of
those features are actively used, for example by Xref commands.  I
don't understand how we can deprecate those parts, let alone remove
them.

Maybe you only meant the parts in CEDET that handle project structure,
i.e. that overlap what project.el does.  Those parts we could perhaps
consider deprecating, especially if we can make CEDET use project.el
instead.  But AFAIR that's a very small part of what we have below
cedet/, functionality-wise.



  reply	other threads:[~2022-05-16 17:15 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
2022-05-16 16:09       ` Ergus
2022-05-16 17:15         ` Eli Zaretskii [this message]
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=83fsl9iel6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=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).