unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Spencer Baugh <sbaugh@janestreet.com>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: 62759-done@debbugs.gnu.org
Subject: bug#62759: [PATCH] add support for prompting for projects by name
Date: Mon, 10 Apr 2023 20:08:19 -0400	[thread overview]
Message-ID: <CAO=BR8N0hteNdxqmJ8Oh+nHoWq4=O33P4=Kx1TikdWc4gEn5Kg@mail.gmail.com> (raw)
In-Reply-To: <2fb028b1-a9ad-648d-9d27-2107e7e4833a@gutov.dev>

[-- Attachment #1: Type: text/plain, Size: 916 bytes --]

On Mon, Apr 10, 2023, 19:20 Dmitry Gutov <dmitry@gutov.dev> wrote:

> Hi! Thanks for the patch. Pushed to master.
>
> Next time please also add the full common message, though.
>

Sorry, will do. I was expecting to need to iterate through some review
cycles :)

Also note that the idea behind the current default (and also why it
> doesn't return a project instance: just the dir) was to avoid visiting
> all the directories -- because some might be unavailable at this exact
> moment (e.g. remote, over Tramp, and currently disconnected), and some
> simply slow.


Yes, I figured that was the reason. I should also mention that I was
thinking about automatically pruning zombie projects (my backend yields
lots of those) but instead I just had project-prompt-project-name skip
zombies, for exactly this reason (that it avoids excess FS access).

It shouldn't hurt to have this as an alternative behavior, though.
>

[-- Attachment #2: Type: text/html, Size: 1720 bytes --]

      reply	other threads:[~2023-04-11  0:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 19:14 bug#62759: [PATCH] add support for prompting for projects by name Spencer Baugh
2023-04-10 23:20 ` Dmitry Gutov
2023-04-11  0:08   ` Spencer Baugh [this message]

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='CAO=BR8N0hteNdxqmJ8Oh+nHoWq4=O33P4=Kx1TikdWc4gEn5Kg@mail.gmail.com' \
    --to=sbaugh@janestreet.com \
    --cc=62759-done@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    /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).