From: Jeff Epler <jepler@unpythonic.net>
To: git@vger.kernel.org
Subject: A note on modern git plus ancient meld ("wrong number of arguments")
Date: Thu, 9 Feb 2012 13:17:43 -0600 [thread overview]
Message-ID: <20120209191742.GA20703@unpythonic.net> (raw)
I note this just in case it helps someone else track down a similar
problem, not because I think any change needs to be made to git, as a
version of meld new enough to not be affected by this problem is 5 years
old.
At $DAYJOB, I recently encountered a problem after upgrading from (don't
laugh) git 1.7.1 to 1.7.8.3: one developer stated that meld failed to
run, instead displaying the error 'Wrong number of arguments (Got 5)'.
We determined that this user was running a very old version of meld
(1.1.1) from his home directory, as opposed to the also very old system
version of meld (1.1.5). It turns out that the check added in
f61bd9c mergetools/meld: Use '--output' when available
fails on meld 1.1.1, leading git to incorrectly believe the --output
flag is supporrted:
$ meld-1.1.1 --output /dev/null --help >/dev/null 2>&1; echo $?
0 # i.e., detected as supported
The test as written gives the correct ("not supported") result with meld
1.1.5:
$ meld-1.1.5 --output /dev/null --help >/dev/null 2>&1; echo $?
2 # i.e., detected as supported
so if you encounter the message 'Wrong number of arguments (Got 5)' from
meld, then check whether you have an ancient version of meld. If for
some reason you can't upgrade to at least 1.1.5, maybe you'd find the
following configuration flags useful:
[merge]
tool = ancientmeld
[mergetool "ancientmeld"]
cmd = meld-1.1.1 \"$LOCAL\" \"$MERGED\" \"$REMOTE\"
Jeff
next reply other threads:[~2012-02-09 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 19:17 Jeff Epler [this message]
2012-02-10 2:42 ` A note on modern git plus ancient meld ("wrong number of arguments") David Aguilar
2012-02-10 8:23 ` Jonathan Nieder
2012-02-10 11:29 ` Sebastian Schuberth
2012-02-10 17:59 ` Jonathan Nieder
2012-02-10 21:28 ` Junio C Hamano
2012-02-10 21:57 ` [PATCH] mergetools/meld: Use --help output to detect --output support Jonathan Nieder
2012-02-10 22:23 ` Jeff Epler
2012-02-10 22:30 ` Jeff Epler
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=20120209191742.GA20703@unpythonic.net \
--to=jepler@unpythonic.net \
--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).