From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#59502: 29.0.50; [PATCH] Dedicated buffers per project Date: Sat, 10 Dec 2022 03:50:56 +0200 Message-ID: <86ea8d5d-1a47-08ff-3e06-ee32d7362211@yandex.ru> References: <87fse7lacm.fsf@gmail.com> <864ju8a5ch.fsf@mail.linkov.net> <9b353f38-9e1d-9bb6-4512-9e4db594a2a6@yandex.ru> <86y1rjveix.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26046"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Cc: Gabriel , 59502@debbugs.gnu.org To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Dec 10 02:52:13 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p3p2C-0006bV-RB for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 10 Dec 2022 02:52:12 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p3p27-0002AK-Ee; Fri, 09 Dec 2022 20:52:07 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p3p23-0002A5-66 for bug-gnu-emacs@gnu.org; Fri, 09 Dec 2022 20:52:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1p3p22-000829-NI for bug-gnu-emacs@gnu.org; Fri, 09 Dec 2022 20:52:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1p3p22-0001iq-FG for bug-gnu-emacs@gnu.org; Fri, 09 Dec 2022 20:52:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 10 Dec 2022 01:52:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 59502 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 59502-submit@debbugs.gnu.org id=B59502.16706370656582 (code B ref 59502); Sat, 10 Dec 2022 01:52:02 +0000 Original-Received: (at 59502) by debbugs.gnu.org; 10 Dec 2022 01:51:05 +0000 Original-Received: from localhost ([127.0.0.1]:39781 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p3p17-0001i6-FB for submit@debbugs.gnu.org; Fri, 09 Dec 2022 20:51:05 -0500 Original-Received: from mail-wr1-f54.google.com ([209.85.221.54]:36503) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p3p16-0001hV-4T for 59502@debbugs.gnu.org; Fri, 09 Dec 2022 20:51:04 -0500 Original-Received: by mail-wr1-f54.google.com with SMTP id h10so6913258wrx.3 for <59502@debbugs.gnu.org>; Fri, 09 Dec 2022 17:51:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=V8RwnR0uKsokxaYOUOMfWpnzxHqLTCWwCRXdkzVEXUg=; b=pdTdocTkh2S3v3o8WekOtfRjjFYJIhZkdH7l4yOf3envPC5myaxaq0xgWqwmDXI9z8 6N3LxtcDaavZJUj375Dzhip10qnXPBiou2MV1fomW0vYZ3YOAkpP3U8bn11yZAiDCqmN 1TdZU+A0pFm8H+STy+qw3N5rIPQfvZ+noSmPH59g+HP7TtRI6dBxZqMcZ6fIXYUi1du+ fHpk135K7ggK6SahSyyIN4ghsd3rtdGJ6G4IIIIP35J7oWLnKrs0iEvkJxwhpak5faT8 EHogvaYQlMbhEpZCpGIncqWZjLFRys5+qNra1G84q46xXCOlZpQGYlDoB194b5LwGYZP 1W2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=V8RwnR0uKsokxaYOUOMfWpnzxHqLTCWwCRXdkzVEXUg=; b=jOWuvdKPTchTNi4lgeAOs9Ch9JZ1kLV9KjSROte+vNZFatRi8+WFyresu2z6plcUFL yfZTnfliIjna7JxixPDB4N0xX9f/0unGqY9AO3TSPAQF1+jfpd9qaUKrTP7HGOcIZew9 /XUkaCurC379fX3nSb3R40qGxyc2CS9QmoyDEPtklQjBnP4xfKnvrKHyXJi6cn2IewFo 30ftds04kmVBKUWxPV3tbJadYD/+B4UixLnjJBN9BfQ+iaJHYXx0+pM8IRQ0ZXQZ76rl ed1hHmxrSMMKOg+kBFTLLGr+CZaifxAD7NSenSZC3xqqBjmDD+A90IKZAuLMRnWRXqde NSLw== X-Gm-Message-State: ANoB5pkT6tqzPliTRIP8yoUAjwDAtUFmKNEXXOHele5D+JHHOuSY7lgf 4deZ7s5ujTTed6m+y6WzPf8= X-Google-Smtp-Source: AA0mqf5f7NOdZ7hUhgeLIKkaRQhYoFBicPNSTMHNsl9kaR29QhmA4NhVstk5EVy+TWriT0jD9005tg== X-Received: by 2002:a5d:4d4b:0:b0:242:6b2f:4988 with SMTP id a11-20020a5d4d4b000000b002426b2f4988mr4471564wru.46.1670637058217; Fri, 09 Dec 2022 17:50:58 -0800 (PST) Original-Received: from [192.168.0.2] ([46.251.119.176]) by smtp.googlemail.com with ESMTPSA id n3-20020a056000170300b002368f6b56desm3231305wrc.18.2022.12.09.17.50.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 09 Dec 2022 17:50:57 -0800 (PST) Content-Language: en-US In-Reply-To: <86y1rjveix.fsf@mail.linkov.net> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:250482 Archived-At: On 07/12/2022 09:50, Juri Linkov wrote: >>> (setopt project-buffer-name-function >>> (lambda (project _command-symbol buffer-name) >>> (format "%s<%s>" buffer-name (project-name project)))) >> I think*prjname/Shell Command Output* sounds nice enough. >> >> If it doesn't, we probably wouldn't choose*Shell Command Output* as the >> name for non-project buffers of this type, would we? > For designing a naming scheme, I suggest to keep in mind that > the users might already have customized the behavior for > displaying these buffers by using display-buffer-alist > that often takes into account a uniquified suffix, e.g.: > > "\\`\\*\\(?:Shell Command Output\\|xref\\|vc-dir\\|compilation\\) > \\*\\(?:<[^>]+>\\)?\\'" > > So for compatibility it would be better to add the project name > in the suffix without changing the standard base buffer names, e.g.: > > "*Shell Command Output*", "*xref*" > > But if you want to add the project name after the first asterisk, > this is easy to do as well with just: > > (setf (substring buffer-name 1 1) (project-name project)) The naming scheme is often affected by the uniquify package, and different people use different ordering. Should we really go there?