From: Dmitry Gutov <dmitry@gutov.dev>
To: Spencer Baugh <sbaugh@janestreet.com>, 63870@debbugs.gnu.org
Subject: bug#63870: 29.0.90; project.el can't dynamically populate the project list
Date: Sat, 17 Jun 2023 05:55:59 +0300 [thread overview]
Message-ID: <aa0618d7-e868-07ae-9cc4-ebe76f9803e1@gutov.dev> (raw)
In-Reply-To: <ierjzwkahgh.fsf@janestreet.com>
Hi!
On 03/06/2023 14:55, Spencer Baugh wrote:
> I'd like a customization point where I can supply a function (or list of
> functions) which project-known-project-roots should run to produce an
> additional list of project root directories, which should then be
> appended to project--list.
Are you sure the existing functions won't cut it? Such as
project-remember-project and project-forget-project.
The names might seem a little wrong, but keeping in mind that
project--list is about having a list of projects "remembered" somewhere,
they're probably fine. And you could let-bind project--list somewhere at
the top level in your function/command/etc, so the list is not altered
in the end.
> I don't need project.el to specifically remember these projects; they'll
> be remembered automatically as users use them, and completing-read will
> nicely deduplicate the project roots anyway.
We could add some var like project-list-no-write, so that dynamic
changes don't get written to disk.
Unless you want to keep the "dynamic" list to be used by regular
commands, that is.
In that case, the above will probably not suffice. We could go with your
approach, or even add some project-list-sources hook.
But how would the entries from different sources (e.g. the list file and
your dynamic list) combined? How will they be sorted?
In case we can't come up with a generic way, we could simply add a
generic storage abstraction (similar to xref-history-storage), which you
would override/advise to combine the lists as needed for your usage.
next prev parent reply other threads:[~2023-06-17 2:55 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 [this message]
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
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=aa0618d7-e868-07ae-9cc4-ebe76f9803e1@gutov.dev \
--to=dmitry@gutov.dev \
--cc=63870@debbugs.gnu.org \
--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).