From: Dmitry Gutov <dgutov@yandex.ru>
To: Gabriel <gabriel376@hotmail.com>, 59502@debbugs.gnu.org
Subject: bug#59502: 29.0.50; [PATCH] Dedicated buffers per project
Date: Fri, 25 Nov 2022 03:37:09 +0200 [thread overview]
Message-ID: <f72f59df-6b52-dd97-f738-2059c19c6078@yandex.ru> (raw)
In-Reply-To: <SJ0PR06MB86090A147EE6E14492A051198B0C9@SJ0PR06MB8609.namprd06.prod.outlook.com>
Hi!
On 23/11/22 07:11, Gabriel wrote:
> In summary, project.el currently has the following behavior and
> customization options:
>
> | Project Command | Generated Buffer | Current Behavior | Customization Options |
> |-----------------------------------+--------------------------+-------------------------------+--------------------------------------------|
> | `project-find-regexp' | "*xref*" | Use a default buffer | Not available |
> | `project-or-external-find-regexp' | "*xref*" | Use a default buffer | Not available |
> | `project-list-buffers' | "*Buffer List*" | Use a default buffer | Not available |
> | `project-kill-buffers' | "*Buffer List*" | Use a default buffer | Not available |
> | `project-shell-command' | "*Shell Command Output*" | Use a default buffer | Not available |
> | `project-async-shell-command' | "*Async Shell Command*" | Use a default buffer | Not available |
> | `project-compile` | "*compilation*" | Use a default buffer | `project-compilation-buffer-name-function' |
> | `project-vc-dir' | "*vc-dir*" | Use a default buffer | Through uniquify.el defcustom's |
> | `project-shell' | "*shell*" | Use a project prefixed buffer | Not available |
> | `project-eshell' | "*eshell*" | Use a project prefixed buffer | Not available |
>
> My suggestion is to improve the consistency of how project-related
> buffers are created and named, providing sufficient customization
> options for users.
This is a nice initiative, and the patch you sent seems to handle most
of the technical issues.
There's one thing, though: some of these buffers might only start to be
project-related, but then "relate" to some different project a little
after. Buffers such as Dired, Shell and Eshell.
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?
next prev parent reply other threads:[~2022-11-25 1:37 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 [this message]
2022-11-25 2:55 ` Gabriel
2022-11-25 8:14 ` Kévin Le Gouguec
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=f72f59df-6b52-dd97-f738-2059c19c6078@yandex.ru \
--to=dgutov@yandex.ru \
--cc=59502@debbugs.gnu.org \
--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).