unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: "Daniel Martín" <mardani29@yahoo.es>, "Juri Linkov" <juri@linkov.net>
Cc: 50489@debbugs.gnu.org
Subject: bug#50489: vc-annotate doesn't keep the current line
Date: Tue, 14 Sep 2021 02:45:30 +0300	[thread overview]
Message-ID: <eab9ed94-d5ea-a06c-1210-6a7efd291444@yandex.ru> (raw)
In-Reply-To: <m1bl4wz6cg.fsf@yahoo.es>

On 13.09.2021 21:19, Daniel Martín via Bug reports for GNU Emacs, the 
Swiss army knife of text editors wrote:
> Juri Linkov<juri@linkov.net>  writes:
> 
>> After 'C-x v g' (vc-annotate), typing 'a' (vc-annotate-revision-previous-to-line)
>> doesn't keep the current line.  For VC archaeology there is a need to traverse
>> the history of the current line by typing a sequence of 'a a a ...'
>> But 'a' doesn't keep the line current, so need to spend time
>> finding the same line in the buffer to be able to type 'a' on it again.
> I think `git blame` provides a --porcelain option that helps track lines
> accross revisions.  I expect that using that information would be an
> improvement over the current behavior, but the solution won't be perfect
> and in some situations it'll still go to a strange line.  Also, I don't
> know if this feature is available in other non-git vc backends.

Interesting suggestion. I think reliance on known line numbers can be 
made optional for backends that do not provide that info.

--porcelain (or --list-porcelain) output is peculiar and not 
customizable, so it would take some work to convert in to the same view 
we are currently enjoying. Hopefully without any loss in performance 
(I'm guessing the slowest part is still going to be the scanning of 
history).





      reply	other threads:[~2021-09-13 23:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 17:43 bug#50489: vc-annotate doesn't keep the current line Juri Linkov
2021-09-09 23:15 ` Dmitry Gutov
2021-09-13 18:19 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-13 23:45   ` Dmitry Gutov [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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=eab9ed94-d5ea-a06c-1210-6a7efd291444@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=50489@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=mardani29@yahoo.es \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).