git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Theodore Tso" <tytso@mit.edu>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: Conflict editing
Date: Mon, 5 Mar 2007 17:48:32 +1300	[thread overview]
Message-ID: <46a038f90703042048m42ec07f6yab41c2a2de410ac9@mail.gmail.com> (raw)
In-Reply-To: <20070305040406.GB26781@thunk.org>

On 3/5/07, Theodore Tso <tytso@mit.edu> wrote:
> On Mon, Mar 05, 2007 at 10:59:33AM +1300, Martin Langhoff wrote:
> > I find xxdiff much better than meld, tkdiff and kdiff -- but maybe I
> > just don't know how to use them, or they have gotten better in the
> > last few months.
>
> I wasn't familiar with xxdiff until just now, but having played with
> it, kdiff3 is much easier for a beginner to use.  The toolbar makes it
> a lot easier to select from one or the other, I find the keyboard
> accellerators to be much more intuitive (although I suppose if you are
> a vi or nethack fan the H, J, K keys will make sense to you :-).

No, I hate that navigation. But arrow keys and pageup/down work great
for me. Mouse navigation is superb too.

> In addition, with xxdiff it gives the user way too many options about
> whether you want to save the left, right, or center, or merged
> windows.

I can understand that. But it also does in-the-line diff colouring
that I haven't seen the others do. Where the lines don't match on
something small, you can see the offending characters in a slightly
different tone (I'm colourblind, so I'm unsure of the exact colour,
but it does work).

I find xxdiff to be an order of magnitude faster than meld and kdiff3.
And at least kdiff3 spews garbage about trying to start the whole of
KDE infrastructure hairball so it messes up my terminal where I had
interesting messages from the just-executed git-pull.

So at least for now xxdiff is my well-behaved, flexible and fast tool ;-)

And I can see at a glance that single quotes got replaced with double
quotes or a trailing space got added or trimmed and _that_'s why the
thing didn't merge cleanly.

> > One thing I _don't_ want as a user is to see the graphical mergers
> > starting by default. Most merges are trivial, and I can just edit them
> > in emacs or vi.
>
> Well, git will handle most merges automatially for you anyway.  You
> would only use git mergetool to handle the merge conflicts.

Sorry -- I meant to say most conflicts are trivial. Someone mentioned
auto-running gui tools on any conflict, and don't think I want that.

cheers,


martin

  reply	other threads:[~2007-03-05  4:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-04 12:43 Conflict editing Johannes Schindelin
2007-03-04 13:29 ` Johannes Schindelin
2007-03-04 18:10 ` Theodore Tso
2007-03-04 21:59   ` Martin Langhoff
2007-03-05  4:04     ` Theodore Tso
2007-03-05  4:48       ` Martin Langhoff [this message]
2007-03-04 23:40 ` Shawn O. Pearce
2007-03-05  6:25 ` Brian Gernhardt
2007-03-05 11:25   ` Johannes Schindelin
2007-03-05 15:07     ` Uwe Kleine-König
2007-03-05 19:27     ` Brian Gernhardt

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=46a038f90703042048m42ec07f6yab41c2a2de410ac9@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).