From: Spencer Baugh <sbaugh@janestreet.com>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: 66518@debbugs.gnu.org, Philip Kaludercic <philipk@posteo.net>
Subject: bug#66518: [PATCH] Use project-name in the project-kill-buffers prompt
Date: Mon, 16 Oct 2023 14:48:42 -0400 [thread overview]
Message-ID: <iera5siiet1.fsf@janestreet.com> (raw)
In-Reply-To: <13f596c0-47e5-ed57-1c96-d659315cb1a4@gutov.dev> (Dmitry Gutov's message of "Sat, 14 Oct 2023 02:41:59 +0300")
Dmitry Gutov <dmitry@gutov.dev> writes:
> On 13/10/2023 19:04, Philip Kaludercic wrote:
>> Spencer Baugh<sbaugh@janestreet.com> writes:
>>
>>> Tags: patch
>>>
>>>
>>> This is mildly prettier.
>> Could this cause confusion, in case two projects share the same name?
>
> I suppose this can indeed be problematic with the default backend,
> where project-name just returns the base name of the root directory
> (and they can conflict).
>
> OTOH, we do use the project name as prefix for buffer names, for
> example. So this might be okay. Worst case, we add a user option
> later.
My contention is that if the user is running this in the current
project, they already basically know where they are, they just need a
little reminder. Plausibly not even that is necessary if they have
project-mode-line enabled. And if they're running it in another
project, using project-switch-project, then they just explicitly
selected a project so we definitely don't need to tell them the full
path of the project they're running in.
next prev parent reply other threads:[~2023-10-16 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 12:36 bug#66518: [PATCH] Use project-name in the project-kill-buffers prompt Spencer Baugh
2023-10-13 16:04 ` Philip Kaludercic
2023-10-13 23:41 ` Dmitry Gutov
2023-10-16 18:48 ` Spencer Baugh [this message]
2023-10-16 23:29 ` 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=iera5siiet1.fsf@janestreet.com \
--to=sbaugh@janestreet.com \
--cc=66518@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=philipk@posteo.net \
/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.