all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: aneesh.kumar@linux.vnet.ibm.com (Aneesh Kumar K.V)
Cc: 6737@debbugs.gnu.org
Subject: bug#6737: 24.0.50; Feature request for vc-annotate.el
Date: Thu, 03 Jun 2021 10:33:48 +0200	[thread overview]
Message-ID: <87fsxz8hzn.fsf@gnus.org> (raw)
In-Reply-To: <m3sk354hwu.fsf@linux.vnet.ibm.com> (Aneesh Kumar K. V.'s message of "Tue, 27 Jul 2010 10:53:29 +0530")

aneesh.kumar@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





      parent reply	other threads:[~2021-06-03  8:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27  5:23 bug#6737: 24.0.50; Feature request for vc-annotate.el Aneesh Kumar K.V
     [not found] ` <handler.6737.B.12802082156511.ack@debbugs.gnu.org>
2010-10-22 11:12   ` bug#6737: Any update ? Aneesh Kumar K. V
2021-06-03  8:33 ` Lars Ingebrigtsen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fsxz8hzn.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=6737@debbugs.gnu.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.