From: Dmitry Gutov <dgutov@yandex.ru>
To: Juri Linkov <juri@linkov.net>
Cc: Matthias Meulien <orontee@gmail.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Name of buffers created by project-shell
Date: Fri, 5 Mar 2021 16:22:14 +0200 [thread overview]
Message-ID: <b682b9d3-935e-ee55-5fee-171d64d6d077@yandex.ru> (raw)
In-Reply-To: <87wnumj1lx.fsf@mail.linkov.net>
On 04.03.2021 19:50, Juri Linkov wrote:
>> There's one problem, though: when called with C-u, the piece of behavior
>> which reads as "create a new inferior shell buffer even if one already
>> exists" now creates buffers uniquely named according to uniquify's rules,
>> which seems to mean
>>
>> *shell*
>> emacs-master/*shell*
>> vc/emacs-master/*shell*
>>
>> instead of what one might expect, like
>>
>> emacs-master/*shell*
>> emacs-master/*shell*<2>
>> emacs-master/*shell*<3>
> For consistency with C-x p v (project-vc-dir) that creates buffers named
>
> *vc-dir*<myproject>
>
> shouldn't C-x p s (project-shell) create buffers with the same style:
>
> *shell*<myproject><1>
> *shell*<myproject><2>
> *shell*<myproject><3>
That's what I said, yes. You just have a different uniquify style
enabled, so the current behavior looks slightly different.
>> Perhaps the solution is not to go through uniquify for this, but then we
>> project-shell can't really be consistent with project-vc-dir.
> 'project-shell' already constructs buffer names using own style,
> so it could switch to another style compatible with
> uniquify-buffer-name-style, then construct buffer names
> like "*shell*<myproject>" and allow uniquify to append
> a numeric suffix <1>, <2>, <3>.
The devil is in the details. To have uniquify do its job properly, I
think we have to call create-file-buffer.
And apparently we need to fix uniquify--create-file-buffer-advice first.
next prev parent reply other threads:[~2021-03-05 14:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 21:18 Name of buffers created by project-shell Matthias Meulien
2021-03-04 3:21 ` Dmitry Gutov
2021-03-04 4:03 ` Stefan Monnier
2021-03-04 17:50 ` Juri Linkov
2021-03-05 14:22 ` Dmitry Gutov [this message]
2021-03-14 13:46 ` Matthias Meulien
2021-03-15 0:41 ` Dmitry Gutov
2021-03-15 13:05 ` Matthias Meulien
2021-03-21 19:44 ` Dmitry Gutov
2021-03-23 20:08 ` Matthias Meulien
2021-03-24 20:12 ` Juri Linkov
2021-03-24 20:47 ` Dmitry Gutov
2021-05-08 17:09 ` Matthias Meulien
2021-05-10 0:08 ` Dmitry Gutov
2021-03-14 13:56 ` Matthias Meulien
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=b682b9d3-935e-ee55-5fee-171d64d6d077@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=orontee@gmail.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).