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

Previous Next

Full log

View this message in rfc822 format

From: Juri Linkov <juri <at> linkov.net>
To: Matthias Meulien <orontee <at> gmail.com>
Cc: Tom Tromey <tom <at> tromey.com>, 21555 <at> debbugs.gnu.org, Sean Whitton <spwhitton <at> spwhitton.name>
Subject: bug#21555: Subject: Re: bug#21555: 25.0.50; per-project *vc-change-log* buffers
Date: Sun, 25 May 2025 09:36:58 +0300

>>>> However, all calls to vc-print-log use this same buffer.
>>>> This seems to be hard-coded in vc.el (vc-print-log-internal).
>>>>
>>>> I would like to be able to make it so that each use of "l" from a
>>>> *vc-dir* buffer gets its own *vc-change-log* buffer; and that "C-x v l"
>>>> in some source file gets a separate buffer.  This way the per-project
>>>> change-log buffers could be relatively long-lived; as it is recomputing
>>>> the data in them takes much too long.
>>>
>>> You can already do something similar by using C-x x u to rename the
>>> *vc-change-log* buffer, and then 'g' inside it works to regenerate it.
>>
>> Or (add-hook 'log-view-mode-hook 'rename-uniquely)
>
> Note that while browsing a change log buffer, when one runs the command
> `log-view-diff', the log buffer is not killed.
>
> For people like me who makes an heavy use of "C-x v l", "C-x v L" and "l"
> in *vc-dir* buffers, it leads to have hundreds of *vc-change-log* buffers
> at the end of the day…

Indeed, hundreds of *vc-change-log* buffers is what I have.
But not a problem.  On the contrary, preserved buffers often help
to check for their previous content.

Previous Next

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