From: Dmitry Gutov <dmitry@gutov.dev>
To: Juri Linkov <juri@linkov.net>, Spencer Baugh <sbaugh@janestreet.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 63870@debbugs.gnu.org
Subject: bug#63870: 29.0.90; project.el can't dynamically populate the project list
Date: Thu, 27 Jul 2023 04:59:32 +0300 [thread overview]
Message-ID: <95b66a01-f1af-d2b7-b10d-72e52c7fd07e@gutov.dev> (raw)
In-Reply-To: <864jm186cb.fsf@mail.linkov.net>
On 18/07/2023 20:41, Juri Linkov wrote:
>> (Maybe I'll revisit this after writing some scripts like this for Emacs
>> development - although those will definitely only be in Elisp, so it
>> would be kind of moot)
> Why can't project--ensure-read-project-list scan a list of known roots
> to find a new project? I.e. the reverse of project-forget-projects-under.
>
> Or like there is an item "... (choose a dir)", another item could be
> "*Rescan*" that will try to find a new project under known roots.
We have an interactive command called 'project-remember-projects-under',
when you want to trigger such a scan.
But as for why we don't do that automatically? Performance, for
instance. Tree traversal, coupled with arbitrary logic for finding
projects, can be too costly.
next prev parent reply other threads:[~2023-07-27 1:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-03 11:55 bug#63870: 29.0.90; project.el can't dynamically populate the project list Spencer Baugh
2023-06-15 19:30 ` Spencer Baugh
2023-06-16 5:45 ` Eli Zaretskii
2023-06-17 2:55 ` Dmitry Gutov
2023-06-27 19:29 ` Spencer Baugh
2023-06-27 19:27 ` Spencer Baugh
2023-06-28 11:24 ` Eli Zaretskii
2023-06-28 12:05 ` Spencer Baugh
2023-06-28 12:18 ` Eli Zaretskii
2023-06-28 12:37 ` Spencer Baugh
2023-06-28 12:56 ` Eli Zaretskii
2023-07-18 2:21 ` Dmitry Gutov
2023-07-18 16:28 ` Spencer Baugh
2023-07-18 17:41 ` Juri Linkov
2023-07-27 1:59 ` Dmitry Gutov [this message]
2023-07-27 1:57 ` 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=95b66a01-f1af-d2b7-b10d-72e52c7fd07e@gutov.dev \
--to=dmitry@gutov.dev \
--cc=63870@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=sbaugh@janestreet.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).