All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Kågedal" <davidk@lysator.liu.se>
To: git@vger.kernel.org
Subject: Re: git-blame.el
Date: Wed, 31 Jan 2007 21:53:31 +0100	[thread overview]
Message-ID: <87ejpazzn8.fsf@morpheus.local> (raw)
In-Reply-To: 864pq7839g.fsf@blue.stonehenge.com

merlyn@stonehenge.com (Randal L. Schwartz) writes:

>>>>>> "David" == David Kågedal <davidk@lysator.liu.se> writes:
>
> David> Here's another version of git-blame.el that automatically tries to
> David> create a sensible list of colors to use for both light and dark
> David> backgrounds.  Plus a few minor fixes.
>
> If this gets traction, this should be what vc-annotate uses on a git file.

I only had a very quick glance, but one "problem" is that vc-annotate
assumes that what you want to do is to run an annotate/blame command
and show the output in another buffer.  My solution is a minor-mode
that shows the blame directly in the edit buffer, and I'm not sure how
easy it would be to convince vc that this is what I want.  And I need
a way to turn it off again, and maybe some local key bindings when it
is active.  This all points to the fact that a minor mode is really
the thing to use.  So maybe I should simply rebind C-x v g to
git-blame-mode instead of vc-annotate...

-- 
David Kågedal

  reply	other threads:[~2007-01-31 20:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31 13:04 git-blame.el David Kågedal
2007-01-31 18:22 ` git-blame.el Randal L. Schwartz
2007-01-31 20:53   ` David Kågedal [this message]
2007-01-31 20:07 ` git-blame.el Junio C Hamano
2007-01-31 20:27   ` git-blame.el David Kågedal
2007-02-01 13:12 ` git-blame.el Karl Hasselström
2007-02-01 13:21   ` git-blame.el David Kågedal
2007-02-01 14:26     ` git-blame.el Karl Hasselström
2007-02-04 20:04 ` [PATCH] git-blame.el --- Minor mode for incremental blame for Git Jakub Narebski

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=87ejpazzn8.fsf@morpheus.local \
    --to=davidk@lysator.liu.se \
    --cc=git@vger.kernel.org \
    /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.
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.