From: Nick Welch <nick@incise.org>
To: David Aguilar <davvid@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Running vimdiff in read-only mode with git-difftool?
Date: Sun, 17 May 2009 23:06:02 -0700 [thread overview]
Message-ID: <9e00fd550905172306w2cc7ab88l82bce0799016fec1@mail.gmail.com> (raw)
In-Reply-To: <20090518055113.GB32259@gmail.com>
As soon as I got your first reply, I started digging and managed to
figure out the $LOCAL and $REMOTE part.
Another interesting issue is that vim doesn't syntax-highlight the temp
file, because the file extension hasn't been carried over to the temp
file's filename. I might see if I can figure out how to hack git to
do that.
Thanks for the help.
Nick
On Sun, May 17, 2009 at 10:51 PM, David Aguilar <davvid@gmail.com> wrote:
> On Sun, May 17, 2009 at 10:01:02PM -0700, Nick Welch wrote:
>> I'm running:
>>
>> git difftool -y --tool=vimdiff -U99999 --patience
>>
>> and I have the following in ~/.gitconfig:
>>
>> [difftool "vimdiff"]
>> cmd = "vimdiff -R"
>
> I forgot to mention a couple of things.
>
>
> If you do change that to e.g. "myvimdiff" you'll need
> the $LOCAL and $REMOTE params as well; probably something
> like:
>
> [difftool "myvimdiff"]
> cmd = vim -R -d -c wincmd l \"$LOCAL\" \"$REMOTE\"
>
>
> $ git difftool -y -t myvimdiff
>
>
> Secondly, git-difftool receives both the pre and post-image
> and doesn't actually receive the output of git-diff, so passing
> --patience unfortunately won't do what you're expecting it to
> do. Piping the output of git-diff to something like kompare(?)
> is probably the only way to get the nice --patience result.
>
> It'd be nice if all diff/merge tools supported the patience
> diff algorithm but that's not the case right now.
>
> --
>
> David
>
>
>
prev parent reply other threads:[~2009-05-18 6:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 5:01 Running vimdiff in read-only mode with git-difftool? Nick Welch
2009-05-18 5:42 ` David Aguilar
2009-05-18 5:51 ` David Aguilar
2009-05-18 6:06 ` Nick Welch [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=9e00fd550905172306w2cc7ab88l82bce0799016fec1@mail.gmail.com \
--to=nick@incise.org \
--cc=davvid@gmail.com \
--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 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).