git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: John Keeping <john@keeping.me.uk>
Cc: David Aguilar <davvid@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH v2 3/4] mergetool--lib: Add functions for finding available tools
Date: Tue, 29 Jan 2013 12:22:48 -0800	[thread overview]
Message-ID: <7vr4l3oi1z.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130129194846.GD1342@serenity.lan> (John Keeping's message of "Tue, 29 Jan 2013 19:48:47 +0000")

John Keeping <john@keeping.me.uk> writes:

> On Sun, Jan 27, 2013 at 04:52:25PM -0800, David Aguilar wrote:
>> --- a/git-mergetool--lib.sh
>> +++ b/git-mergetool--lib.sh
>> @@ -2,6 +2,35 @@
>>  # git-mergetool--lib is a library for common merge tool functions
>>  MERGE_TOOLS_DIR=$(git --exec-path)/mergetools
>>  
>> +mode_ok () {
>> +	diff_mode && can_diff ||
>> +	merge_mode && can_merge
>> +}
>> +
>> +is_available () {
>> +	merge_tool_path=$(translate_merge_tool_path "$1") &&
>> +	type "$merge_tool_path" >/dev/null 2>&1
>> +}
>> +
>> +show_tool_names () {
>> +	condition=${1:-true} per_line_prefix=${2:-} preamble=${3:-}
>> +
>> +	( cd "$MERGE_TOOLS_DIR" && ls -1 * ) |
>
> Is the '*' necessary here?

No, it was just from a bad habit (I have ls aliased to ls -A or ls
-a in my interactive environment, which trained my fingers to this).

I also think you can lose -1, although it does not hurt.
>> +	tool_opt="'git ${TOOL_MODE}tool --tool-<tool>'"
>> +	available=$(show_tool_names 'mode_ok && is_available' '\t\t' \
>> +		"$tool_opt may be set to one of the following:")
>> +	unavailable=$(show_tool_names 'mode_ok && ! is_available' '\t\t' \
>> +		"The following tools are valid, but not currently available:")
>>  	if test -n "$available"
>>  	then
>> -		echo "'git $cmd_name --tool=<tool>' may be set to one of the following:"
>> -		echo "$available" | sort | sed -e 's/^/	/'
>> +		echo "$available"
>>  	else
>>  		echo "No suitable tool for 'git $cmd_name --tool=<tool>' found."
>>  	fi
>>  	if test -n "$unavailable"
>>  	then
>>  		echo
>> -		echo 'The following tools are valid, but not currently available:'
>> -		echo "$unavailable" | sort | sed -e 's/^/	/'
>> +		echo "$unavailable"
>>  	fi
>>  	if test -n "$unavailable$available"
>>  	then
>
> You haven't taken full advantage of the simplification Junio suggested
> in response to v1 here.  We can change the "unavailable" block to be:
>
>     show_tool_names 'mode_ok && ! is_available' "$TAB$TAB" \
>         "${LF}The following tools are valid, but not currently available:"

Actually I was hoping that we can enhance show_tool_names so that we
can do without the $available and $unavailable variables at all.

> If you also add a "not_found_msg" parameter to show_tool_names then the
> "available" case is also simplified:
>
>     show_tool_names 'mode_ok && is_available' "$TAB$TAB" \
>         "$tool_opt may be set to one of the following:" \
>         "No suitable tool for 'git $cmd_name --tool=<tool>' found."
>
> with this at the end of show_tool_names:
>
>     test -n "$preamble" && test -n "$not_found_msg" && \
>         echo "$not_found_msg"

Yes, something along that line.

  reply	other threads:[~2013-01-29 20:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28  0:52 [PATCH v2 0/4] Auto-generate mergetool lists David Aguilar
2013-01-28  0:52 ` [PATCH v2 1/4] mergetool--lib: Simplify command expressions David Aguilar
2013-01-28  0:52   ` [PATCH v2 2/4] mergetool--lib: Improve the help text in guess_merge_tool() David Aguilar
2013-01-28  0:52     ` [PATCH v2 3/4] mergetool--lib: Add functions for finding available tools David Aguilar
2013-01-28  0:52       ` [PATCH v2 4/4] doc: Generate a list of valid merge tools David Aguilar
2013-01-28  2:14         ` Junio C Hamano
2013-01-28 19:37       ` [PATCH v2 3/4] mergetool--lib: Add functions for finding available tools John Keeping
2013-01-28 20:36         ` Junio C Hamano
2013-01-29 19:48       ` John Keeping
2013-01-29 20:22         ` Junio C Hamano [this message]
2013-01-29 22:27           ` David Aguilar
2013-01-29 22:55             ` Junio C Hamano
2013-01-29 23:06               ` John Keeping
2013-01-30  3:08                 ` Junio C Hamano
2013-01-30  3:34                   ` Junio C Hamano
2013-01-29 23:02             ` John Keeping
2013-01-29 19:22   ` [PATCH v2 1/4] mergetool--lib: Simplify command expressions John Keeping
2013-01-29 22:09     ` David Aguilar
2013-01-29 22:27       ` Junio C Hamano
2013-01-30  6:20         ` [PATCH v3 1/4] mergetool--lib: simplify " David Aguilar
2013-01-30  7:04           ` Junio C Hamano
2013-01-28  2:08 ` [PATCH v2 0/4] Auto-generate mergetool lists Junio C Hamano
2013-01-28  2:21   ` David Aguilar
2013-01-28  2:27     ` Junio C Hamano
2013-01-28  2:41       ` David Aguilar
2013-01-28  2:53         ` Junio C Hamano
2013-01-28 21:01         ` John Keeping
2013-01-28 21:50           ` Junio C Hamano
2013-01-28 22:21             ` John Keeping
2013-01-29 11:56               ` Joachim Schmitz
2013-01-29 12:09                 ` John Keeping
2013-01-29 16:15                   ` Junio C Hamano
2013-01-29 16:46                     ` John Keeping
2013-01-28  8:20 ` Philip Oakley
2013-01-28  9:16   ` David Aguilar
2013-01-28 21:19     ` Philip Oakley

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=7vr4l3oi1z.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=john@keeping.me.uk \
    /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).