GNU bug report logs - #21555
25.0.50; per-project *vc-change-log* buffers

Previous Next

Full log

Message #60 received at 21555 <at> debbugs.gnu.org (full text, mbox):

From: Juri Linkov <juri <at> linkov.net>
To: Matthias Meulien <orontee <at> gmail.com>
Cc: Dmitry Gutov <dmitry <at> gutov.dev>, Tom Tromey <tom <at> tromey.com>,
 21555 <at> debbugs.gnu.org, Sean Whitton <spwhitton <at> spwhitton.name>
Subject: Re: Subject: Re: bug#21555: 25.0.50; per-project *vc-change-log*
 buffers
Date: Mon, 09 Jun 2025 09:29:20 +0300

>     >     Although such prefixes are still removed after reverting
>     >     the compilation buffer.  
>     >
>     > I can't reproduce that. When pressing `g' key in a
>     > `*myproject-compilation*'
>     > buffer (mapped to `recompile'), the buffer name doesn't change.
>
>     Since (add-hook 'compilation-mode-hook 'rename-uniquely) doesn't work
>     for creating unique buffer names I'm using this instead:
>
>     (setq compilation-buffer-name-function
>           (lambda (name-of-mode)
>             (generate-new-buffer-name
>              (concat "*" (downcase name-of-mode) "*"))))
>
>     but it removes the project prefix on `g'.
>
> Starting with 28.1, one can use :
> (setq project-compilation-buffer-name-function
> 'project-prefixed-buffer-name)

This setting doesn't produce unique buffer names
for every new compilation with added prefixes <1>, <2>, ...

Does your path support such use cases when
'rename-uniquely' is used in a hook to add <1>, <2>?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.