unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Matthias Meulien <orontee@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>, Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: Name of buffers created by project-shell
Date: Wed, 24 Mar 2021 22:12:33 +0200	[thread overview]
Message-ID: <874kh0v1gi.fsf@mail.linkov.net> (raw)
In-Reply-To: <87h7l163bo.fsf@gmail.com> (Matthias Meulien's message of "Tue, 23 Mar 2021 21:08:11 +0100")

>> Attaching the updated patch which fixes that particular problem,
>> though I'm a little more suspicious of some of uniquify's choices now.
>
> I confirm that with that patch names of buffers created using
> `project-shell' (without using C-u) are correct.

Please define "correct".  Correct in the sense that it works only without C-u?
Because while currently buffer names created with C-u are nicely formatted:

project1:
- *project1-shell*
- *project1-shell*<2>
- *project1-shell*<3>

project2:
- *project2-shell*
- *project2-shell*<2>
- *project2-shell*<3>

But after the change buffers created by 'C-u project-shell' are quite messy:

project1:
- *shell*
- *shell*<2>
- *shell*<4>

project2:
- *shell*<project2>
- *shell*<3>
- *shell*<5>



  reply	other threads:[~2021-03-24 20:12 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
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 [this message]
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=874kh0v1gi.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --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).