Subject: Re: bug#21555: Subject: Re: bug#21555: 25.0.50; per-project *vc-change-log* buffers

From: Eli Zaretskii <[email-masked]>
Date: Sun, 25 May 2025 09:23:49 +0300

> Cc: [email-masked]
> From: Matthias Meulien <[email-masked]>
> Date: Sat, 24 May 2025 21:58:20 +0200
> 
> 
> Juri Linkov <[email-masked]> writes:
> 
> >>> 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…

Why having many such buffers a problem?  We have features (like
midnight.el) to kill unused buffers, if the user doesn't want to do
that manually.

Anyway, it sounds like there are already solutions for this issue, so
should we close it now?