From: Theodore Tso <tytso@mit.edu>
To: Steffen Prohaska <prohaska@zib.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] mergetool: make Apple's FileMerge available as a merge_tool
Date: Sun, 17 Jun 2007 14:12:00 -0400 [thread overview]
Message-ID: <20070617181200.GA15218@thunk.org> (raw)
In-Reply-To: <B12626B9-766E-4EA4-888F-B3E2DA889D15@zib.de>
On Sun, Jun 17, 2007 at 06:13:11PM +0200, Steffen Prohaska wrote:
>
> Hmm, now I found out that opendiff, which was already available
> as an option, actually launches FileMerge.
Yep.
> I wasn't aware of this fact. git-mergetool proposed to use vimdiff
> although I had preferred the graphical application FileMerge, which
> would have been launched by opendiff.
Do you know of a way of determining whether or not under MacOS X, a
program can easily determine whether or not the user is sitting in
front of the graphical display, as opposed to coming in via an SSH
connection?
If so, we could use that under MacOS to make the defaults be to use
opendiff under those circumstances.
Realistically, though, past a certain point we can only be so smart
with the hueristics. If you know what you want, you should really set
the merge.tool config option in your ~/.gitconfig file, and be done
with it.
> Don't know if my patch makes any sense. Probably a note in the
> documentation that opendiff launches the GUI would be nice.
Maybe a change so that opendiff is listed as "opendiff (aka
FileMerge)", perhaps?
- Ted
next prev parent reply other threads:[~2007-06-17 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 15:59 [PATCH] mergetool: make Apple's FileMerge available as a merge_tool Steffen Prohaska
2007-06-17 16:13 ` Steffen Prohaska
2007-06-17 18:12 ` Theodore Tso [this message]
2007-06-17 19:20 ` Steffen Prohaska
2007-06-18 9:39 ` Scott Lamb
2007-06-18 13:18 ` Theodore Tso
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=20070617181200.GA15218@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=prohaska@zib.de \
/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).