From: Jakub Narebski <jnareb@gmail.com>
To: "Richard Quirk" <richard.quirk@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: help with git usage
Date: Wed, 30 Apr 2008 03:39:34 -0700 (PDT) [thread overview]
Message-ID: <m3hcdjocdc.fsf@localhost.localdomain> (raw)
In-Reply-To: <cac9e4380804300122v4f23251cqbc36640a07379c8@mail.gmail.com>
"Richard Quirk" <richard.quirk@gmail.com> writes:
> On Tue, Apr 29, 2008 at 7:37 PM, Daniel Quinlan <danq@brtt.com> wrote:
>
>> 3) Similarly, I can't use the little context diffs I can see in
>> git-gui -- I need to see side by side comparisons; I've become
>> accustomed to tkdiff. It seems like git mergetool knows how to do
>> that in some restricted circumstances, but I want to do it outside
>> the context of a merge.
>
> If you use Vim, I'd recommend the vcscommand plugin - see
> http://code.google.com/p/vcscommand/ - which has fairly recently added
> git support. Once installed :VCSVimDiff shows the diff side by side
> between working copy and HEAD (by default, or whatever revision you
> tell it) like a regular vimdiff between files.
Could you add infomration about this to Git Wiki
http://git.or.cz/gitwiki/InterfacesFrontendsAndTools
somewhere in "Editors and IDE integration" subsection?
TIA
--
Jakub Narebski
GNU Emacs user
next prev parent reply other threads:[~2008-04-30 10:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 17:37 help with git usage Daniel Quinlan
2008-04-29 18:07 ` Daniel Barkalow
2008-04-30 7:39 ` Jakub Narebski
2008-05-07 22:41 ` Daniel Quinlan
2008-05-08 0:16 ` Julian Phillips
2008-05-08 20:01 ` Dirk Süsserott
2008-05-08 23:07 ` Jakub Narebski
2008-04-30 12:02 ` Matt Graham
2008-04-30 13:09 ` Andreas Ericsson
2008-04-30 8:22 ` Richard Quirk
2008-04-30 10:39 ` Jakub Narebski [this message]
2008-04-30 11:50 ` Richard Quirk
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=m3hcdjocdc.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=richard.quirk@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).