GNU bug report logs - #6737
24.0.50; Feature request for vc-annotate.el

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 6737 in the body.
You can then email your comments to 6737 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

From: aneesh.kumar <at> linux.vnet.ibm.com (Aneesh Kumar K.V)
To: bug-gnu-emacs <at> gnu.org
Subject: 24.0.50; Feature request for vc-annotate.el
Date: Tue, 27 Jul 2010 10:53:29 +0530

It would be nice to support incremental blame support in vc-annotate.el.
Currently we have to wait for the full blame information before the
annotate buffer is available. git blame support incremental blame
feature which should be used to imporve the user experience. A similar
implementation can be found at git://git.bunkus.org/mo-git-blame.git

-aneesh

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

From: "Aneesh Kumar K. V" <aneesh.kumar <at> linux.vnet.ibm.com>
To: 6737 <at> debbugs.gnu.org
Subject: Any update ?
Date: Fri, 22 Oct 2010 16:42:04 +0530

Any update on this bug ? For a source repo with large history this
really make the annotation slow. There is a example of how do to do this
in elisp at 

http://www.bunkus.org/cgi-bin/gitweb.cgi?p=mo-git-blame.git;a=summary

-aneesh

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: aneesh.kumar <at> linux.vnet.ibm.com (Aneesh Kumar K.V)
Cc: 6737 <at> debbugs.gnu.org
Subject: Re: bug#6737: 24.0.50; Feature request for vc-annotate.el
Date: Thu, 03 Jun 2021 10:33:48 +0200

aneesh.kumar <at> linux.vnet.ibm.com (Aneesh Kumar K.V) writes:

> It would be nice to support incremental blame support in vc-annotate.el.
> Currently we have to wait for the full blame information before the
> annotate buffer is available. git blame support incremental blame
> feature which should be used to imporve the user experience. A similar
> implementation can be found at git://git.bunkus.org/mo-git-blame.git

(I'm going through old bug reports that unfortunately got no response at
the time.)

vc-annotate seems to work quite fast for me (even in huge files that
have decades-long histories, as in Emacs), so I'm not sure adding
support for incremental annotation would be worth it.

But perhaps changing the function to only work on the narrowed portion
of the buffer would be nice?  That way you could `C-x n d C-x v g' (for
instance) and get a very snappy annotation of just the current function,
for instance.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #16 received at 6737-close <at> debbugs.gnu.org (full text, mbox):

From: Sean Whitton <spwhitton <at> spwhitton.name>
To: 6737-close <at> debbugs.gnu.org
Subject: Re: bug#6737: 24.0.50; Feature request for vc-annotate.el
Date: Fri, 14 Mar 2025 14:11:07 +0800

Hello,

On Thu 03 Jun 2021 at 10:33am +02, Lars Ingebrigtsen wrote:

> aneesh.kumar <at> linux.vnet.ibm.com (Aneesh Kumar K.V) writes:
>
>> It would be nice to support incremental blame support in vc-annotate.el.
>> Currently we have to wait for the full blame information before the
>> annotate buffer is available. git blame support incremental blame
>> feature which should be used to imporve the user experience. A similar
>> implementation can be found at git://git.bunkus.org/mo-git-blame.git
>
> (I'm going through old bug reports that unfortunately got no response at
> the time.)
>
> vc-annotate seems to work quite fast for me (even in huge files that
> have decades-long histories, as in Emacs), so I'm not sure adding
> support for incremental annotation would be worth it.
>
> But perhaps changing the function to only work on the narrowed portion
> of the buffer would be nice?  That way you could `C-x n d C-x v g' (for
> instance) and get a very snappy annotation of just the current function,
> for instance.

It's been fifteen years since the original report.  Git has probably had
numerous performance improvements made; machines have got faster; the
Git repository with sample code 404s; adding this incremental support
might complicate debugging.  So I'm closing this one.

-- 
Sean Whitton

Previous Next

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