From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Gabriel <gabriel376@hotmail.com>, 59502@debbugs.gnu.org
Subject: bug#59502: 29.0.50; [PATCH] Dedicated buffers per project
Date: Fri, 25 Nov 2022 09:14:17 +0100 [thread overview]
Message-ID: <87fse7lacm.fsf@gmail.com> (raw)
In-Reply-To: <f72f59df-6b52-dd97-f738-2059c19c6078@yandex.ru> (Dmitry Gutov's message of "Fri, 25 Nov 2022 03:37:09 +0200")
Dmitry Gutov <dgutov@yandex.ru> writes:
> For the rest, this probably makes sense. I do wish we had an "upvote"
> button on these threads, to see how many people are interested in
> this.
>
> Anyone would like to +1?
👍
I'd say solution 3) is the one I'm most attracted to.
Idly wondering if it'd make sense to also pass the major-mode to
project-buffer-name-function, since string matching might be unreliable
in some situations? Can't think of any concrete problem off the top of
my head, I just have a vague expectation that mode symbols might be more
stable than buffer names. It's unsubstantiated though, so feel free to
dismiss.
FWIW I think the "serving suggestion" from the OP…
> (setopt project-buffer-name-function
> (lambda (name)
> (format "*%s-%s*"
> (project-name (project-current))
> name)))
… would make sense as a defcustom alternative (and could then be re-used
by project-buffer-name-default).
Thanks Gabriel!
next prev parent reply other threads:[~2022-11-25 8:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 5:11 bug#59502: 29.0.50; [PATCH] Dedicated buffers per project Gabriel
2022-11-25 1:37 ` Dmitry Gutov
2022-11-25 2:55 ` Gabriel
2022-11-25 8:14 ` Kévin Le Gouguec [this message]
2022-11-25 13:27 ` Gabriel
2022-12-06 17:21 ` Juri Linkov
2022-12-07 2:31 ` Dmitry Gutov
2022-12-07 7:50 ` Juri Linkov
2022-12-10 1:50 ` Dmitry Gutov
2022-12-10 17:34 ` Juri Linkov
2022-12-04 23:50 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-25 7:09 ` daanturo
2022-12-05 2:35 ` Dmitry Gutov
2022-12-06 17:23 ` Juri Linkov
2022-12-07 2:35 ` 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=87fse7lacm.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=59502@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=gabriel376@hotmail.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).