From: Junio C Hamano <gitster@pobox•com>
To: David Aguilar <davvid@gmail•com>
Cc: Felipe Contreras <felipe.contreras@gmail•com>,
git@vger•kernel.org, Charles Bailey <charles@hashpling•org>
Subject: Re: [PATCH 2/2] mergetool: run prompt only if guessed tool
Date: Tue, 22 Apr 2014 10:19:51 -0700 [thread overview]
Message-ID: <xmqqbnvt703s.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140422045951.GA60610@gmail.com> (David Aguilar's message of "Mon, 21 Apr 2014 21:59:52 -0700")
David Aguilar <davvid@gmail•com> writes:
> [Cc:ing Charles in case he has an opinion, this behavior dates back to the original MT]
>
> On Sun, Apr 20, 2014 at 07:17:34PM -0500, Felipe Contreras wrote:
>> It's annoying to see the prompt:
>>
>> Hit return to start merge resolution tool (foo):
>>
>> Every time the user does 'git mergetool' even if the user already
>> configured 'foo' as the wanted tool.
>>
>> Display this prompt only when the user hasn't explicitly configured a
>> tool.
>
> I agree this is probably helpful.
> Most users I've met end up configuring mergetool.prompt=false.
>
> Thanks
OK, is it an Ack?
Thanks for CC'ing Charles, by the way. I think his point about
mentioning the change of default somewhere in the documentation
has some merits, and it can be done in a follow-up patch on top.
>> Signed-off-by: Felipe Contreras <felipe.contreras@gmail•com>
>> ---
>> git-mergetool.sh | 14 +++++++++++---
>> 1 file changed, 11 insertions(+), 3 deletions(-)
>>
>> diff --git a/git-mergetool.sh b/git-mergetool.sh
>> index 332528f..d08dc92 100755
>> --- a/git-mergetool.sh
>> +++ b/git-mergetool.sh
>> @@ -277,7 +277,7 @@ merge_file () {
>> echo "Normal merge conflict for '$MERGED':"
>> describe_file "$local_mode" "local" "$LOCAL"
>> describe_file "$remote_mode" "remote" "$REMOTE"
>> - if "$prompt" = true
>> + if test "$guessed_merge_tool" = true || test "$prompt" = true
>> then
>> printf "Hit return to start merge resolution tool (%s): " "$merge_tool"
>> read ans || return 1
>> @@ -315,7 +315,8 @@ merge_file () {
>> return 0
>> }
>>
>> -prompt=$(git config --bool mergetool.prompt || echo true)
>> +prompt=$(git config --bool mergetool.prompt)
>> +guessed_merge_tool=false
>>
>> while test $# != 0
>> do
>> @@ -373,7 +374,14 @@ prompt_after_failed_merge () {
>>
>> if test -z "$merge_tool"
>> then
>> - merge_tool=$(get_merge_tool "$merge_tool") || exit
>> + # Check if a merge tool has been configured
>> + merge_tool=$(get_configured_merge_tool)
>> + # Try to guess an appropriate merge tool if no tool has been set.
>> + if test -z "$merge_tool"
>> + then
>> + merge_tool=$(guess_merge_tool) || exit
>> + guessed_merge_tool=true
>> + fi
>> fi
>> merge_keep_backup="$(git config --bool mergetool.keepBackup || echo true)"
>> merge_keep_temporaries="$(git config --bool mergetool.keepTemporaries || echo false)"
>> --
>> 1.9.2+fc1.1.g5c924db
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger•kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-04-22 17:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 0:17 [PATCH 0/2] Simple default fixes for v2.0 Felipe Contreras
2014-04-21 0:17 ` [PATCH 1/2] merge: enable defaulttoupstream by default Felipe Contreras
2014-04-22 19:53 ` Junio C Hamano
2014-04-21 0:17 ` [PATCH 2/2] mergetool: run prompt only if guessed tool Felipe Contreras
2014-04-22 4:59 ` David Aguilar
2014-04-22 6:01 ` Charles Bailey
2014-04-22 6:24 ` Felipe Contreras
2014-04-22 6:55 ` Charles Bailey
2014-04-22 6:53 ` Felipe Contreras
2014-04-22 7:30 ` Charles Bailey
2014-04-22 7:56 ` Felipe Contreras
2014-04-23 7:56 ` Charles Bailey
2014-04-23 17:07 ` Junio C Hamano
2014-04-24 18:30 ` Junio C Hamano
2014-04-22 17:19 ` Junio C Hamano [this message]
2014-04-23 7:58 ` David Aguilar
2014-04-23 16:52 ` Junio C Hamano
2014-04-22 17:32 ` Junio C Hamano
2014-04-22 19:55 ` Junio C Hamano
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=xmqqbnvt703s.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=charles@hashpling$(echo .)org \
--cc=davvid@gmail$(echo .)com \
--cc=felipe.contreras@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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