From: "David Kågedal" <davidk@lysator.liu.se>
To: git@vger.kernel.org
Cc: Jakub Narebski <jnareb@gmail.com>
Subject: Re: [PATCH 7/7] git-blame.el: Autoupdate while editing
Date: Fri, 09 Feb 2007 12:05:51 +0100 [thread overview]
Message-ID: <87veiboak0.fsf@morpheus.local> (raw)
In-Reply-To: eqhfqv$bnu$1@sea.gmane.org
Jakub Narebski <jnareb@gmail.com> writes:
> [Cc: git@vger.kernel.org]
>
> David K?gedal wrote:
>
>> This adds the support for automatically updating the buffer while editing.
>> A configuration variable git-blame-autoupdate controls whether this should
>> be enabled or not.
>
> Can we use -L option of git-blame for this?
We do.
> BTW did you take a look at Font Lock modes: Fast Lock mode, Lazy Lock mode,
> Just-in-time Lock mode?
I know of them (I use lazy-lock-mode, which I think is the
default). But what do you want me to look at?
--
David Kågedal
prev parent reply other threads:[~2007-02-09 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 8:22 [PATCH 7/7] git-blame.el: Autoupdate while editing David Kågedal
2007-02-09 9:46 ` Jakub Narebski
2007-02-09 11:05 ` David Kågedal [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=87veiboak0.fsf@morpheus.local \
--to=davidk@lysator.liu.se \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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.
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 NNTP newsgroup(s).