From: Lars Ingebrigtsen <larsi@gnus.org>
To: aneesh.kumar@linux.vnet.ibm.com (Aneesh Kumar K.V)
Cc: 6745@debbugs.gnu.org, Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#6745: 24.0.50; vc-annotate should allow to configure the width of blame info
Date: Mon, 09 May 2022 18:16:35 +0200 [thread overview]
Message-ID: <87ee124r6k.fsf@gnus.org> (raw)
In-Reply-To: <m3zkxbpsfk.fsf@linux.vnet.ibm.com> (Aneesh Kumar K. V.'s message of "Wed, 28 Jul 2010 20:25:11 +0530")
aneesh.kumar@linux.vnet.ibm.com (Aneesh Kumar K.V) writes:
> This is with vc-git.el. With C-x v g it would be nice to be able to
> customize the width of blame info. That allows to see both the code
> and associate sha1 on the same window.
Yes, that would be great. It has also been suggested that all the VC
backends should use the same format, and I think that could be done at
the same time. (Even if they don't all have the same data available,
they generally have much in common.)
But to do that, I think we'd have to rework how vc-*-annotate-command
works. I think they basically work by running the "blame" command for
the VC in a buffer, and then parsing/fontifying the output a bit?
To allow regularisation (and user customisation) of the output, I think
we'd have to redo that completely. Instead the backends would dump the
output to a temp dir, we'd parse it completely, add it to some
structure, and then output the data into a buffer in the format we want.
(Something that looks a bit like tabulated-list-mode, but where the user
can, for instance, use commands to make columns disappear and appear as
they wish.)
I think that's more than doable, and worth doing.
I wonder whether anybody's had any concrete ideas in this direction
before (so I've added Dmitry to the CCs).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-09 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 14:55 bug#6745: 24.0.50; vc-annotate should allow to configure the width of blame info Aneesh Kumar K.V
2022-05-09 16:16 ` Lars Ingebrigtsen [this message]
2022-05-09 18:35 ` Lars Ingebrigtsen
2022-05-11 16:53 ` Juri Linkov
2022-05-11 18:40 ` Lars Ingebrigtsen
2022-06-04 18:46 ` Dmitry Gutov
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=87ee124r6k.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=6745@debbugs.gnu.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dgutov@yandex.ru \
/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.