From: "Ping Yin" <pkufranky@gmail.com>
To: "Matthieu Moy" <Matthieu.Moy@imag.fr>
Cc: "David Aguilar" <davvid@gmail.com>, git@vger.kernel.org
Subject: Re: git-difftool
Date: Thu, 1 Jan 2009 15:38:38 +0800 [thread overview]
Message-ID: <46dff0320812312338i5a3ee0cem702a6b67ef76e48c@mail.gmail.com> (raw)
In-Reply-To: <vpqhc4kz5zh.fsf@bauges.imag.fr>
On Thu, Jan 1, 2009 at 12:04 AM, Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
> David Aguilar <davvid@gmail.com> writes:
>
>> The usual use case for this script is when you have either
>> staged or unstaged changes and you'd like to see the changes
>> in a side-by-side diff viewer (e.g. xxdiff, tkdiff, etc).
>>
>> git difftool [<filename>*]
>
> Is it not a complex way of saying
>
> GIT_EXTERNAL_DIFF=xxdiff git diff
$ cat mydiff
#!/bin/bash
exec vimdiff $2 $5
then i run
$ GIT_EXTERNAL_DIFF=mydiff git diff
but it gives me the error
Vim: Warning: Output is not to a terminal
$ ps -ef | grep vimdiff
ping 20284 20283 1 15:37 pts/13 00:00:00 vimdiff
/tmp/.diff_XXXQK6 index.php
next prev parent reply other threads:[~2009-01-01 7:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 1:30 git-difftool David Aguilar
2008-12-31 16:04 ` git-difftool Matthieu Moy
2008-12-31 20:11 ` git-difftool David Aguilar
2008-12-31 21:20 ` git-difftool Boyd Stephen Smith Jr.
2009-01-01 17:58 ` git-difftool Matthieu Moy
2009-01-02 0:13 ` git-difftool Markus Heidelberg
2009-01-02 16:10 ` git-difftool Matthieu Moy
2009-01-02 17:39 ` git-difftool David Aguilar
2009-01-15 22:26 ` git-difftool Markus Heidelberg
2009-01-16 5:05 ` git-difftool David Aguilar
2009-01-01 7:38 ` Ping Yin [this message]
2009-01-02 0:04 ` git-difftool Markus Heidelberg
2009-01-02 1:59 ` git-difftool Ping Yin
2009-01-17 3:47 ` git-difftool enso
2009-01-17 4:41 ` git-difftool David Aguilar
2009-01-17 14:17 ` git-difftool Ping Yin
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46dff0320812312338i5a3ee0cem702a6b67ef76e48c@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).