unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Stephen Leake <stephen_leake@stephe-leake.org>, 48747@debbugs.gnu.org
Subject: bug#48747: 28.0.50; add project-name generic
Date: Fri, 15 Jul 2022 13:48:02 +0200	[thread overview]
Message-ID: <87zghak365.fsf@gnus.org> (raw)
In-Reply-To: <72c3ec98-632b-b8ae-53b9-fdcb3b85f111@yandex.ru> (Dmitry Gutov's message of "Mon, 7 Jun 2021 05:08:34 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

>> In project.el, add a 'project-name' cl-defgeneric, to be used in prompts
>> and other situations where the user is asked to identify a project.
>> It must return a string, which is nominally unique among the user's
>> various projects.
>> The default could be 'project-root'.
>
> Would you like to attach a patch that includes the places where we
> would use the new method?
>
> project-prefixed-buffer-name?

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

This was a year ago, and the original bug report didn't really include a
rationale for the cl-defgeneric.  Stephen, what would you use this for?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-07-15 11:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-30 17:38 bug#48747: 28.0.50; add project-name generic Stephen Leake
2021-06-07  2:08 ` Dmitry Gutov
2022-07-15 11:48   ` Lars Ingebrigtsen [this message]
2022-07-15 13:09     ` Stephen Leake
2022-11-20 22:17 ` bug#48747: " Stephen Leake
2022-11-20 22:57   ` Dmitry Gutov
2022-11-21 18:59     ` bug#48747: [SPAM UNSURE] " Stephen Leake
2022-11-22  2:41       ` Dmitry Gutov
2022-11-22 19:02         ` Stephen Leake
2022-11-22 22:20           ` 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=87zghak365.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=48747@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=stephen_leake@stephe-leake.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 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).