From: Dmitry Gutov <dgutov@yandex.ru>
To: Pankaj Jangid <pankaj@codeisgreat.org>
Cc: 46202@debbugs.gnu.org
Subject: bug#46202: 28.0.50; project-find-file performance degrades significantly with ede-enable-generic-projects
Date: Tue, 2 Feb 2021 00:55:00 +0200 [thread overview]
Message-ID: <ed91e0dc-61f8-5412-5911-bb9ac0a7e37f@yandex.ru> (raw)
In-Reply-To: <m2y2g7lpoc.fsf@codeisgreat.org>
On 01.02.2021 18:26, Pankaj Jangid wrote:
> I was just following the video tutorial from Anand Tamariya for
> configuring Emacs for Java coding. It suggested EDE. Earlier, when I
> read about EDE, it was mostly related to C/C++ files. So I didn’t touch
> at that time.
>
> But now when I enabled generic projects, it affected my other
> workflow. So I disabled it again. I am happy with just the project.el.
Did it have an explanation for which effect ede-enable-generic-projects
was going to have?
>> Would anybody miss EDE <-> project.el integration, do you think?
>>
>> We could remove it or, I suppose, deprioritize over the VC-based backend.
>
> Yes. I think EDE should be disabled/ deprioritized in favour of
> project.el.
I'd like some help with choosing between these options.
>> For a workaround, try:
>>
>> (with-eval-after-load 'ede
>> (remove-hook 'project-find-functions #'project-try-ede))
>>
>
> This workaround did not work.
Hmm. What's your value of project-find-functions?
And which file/package was project-try-ede defined in, if any? If you're
next prev parent reply other threads:[~2021-02-01 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 4:38 bug#46202: 28.0.50; project-find-file performance degrades significantly with ede-enable-generic-projects Pankaj Jangid
2021-02-01 12:08 ` Dmitry Gutov
2021-02-01 16:26 ` Pankaj Jangid
2021-02-01 22:55 ` Dmitry Gutov [this message]
2021-02-02 3:02 ` Pankaj Jangid
2021-02-18 3:12 ` 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=ed91e0dc-61f8-5412-5911-bb9ac0a7e37f@yandex.ru \
--to=dgutov@yandex.ru \
--cc=46202@debbugs.gnu.org \
--cc=pankaj@codeisgreat.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.